From: "Maxim Yu. Osipov" <mosipov@ilbers.de>
To: claudius.heine.ext@siemens.com, isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: Re: [PATCH 0/2] Fix of #56
Date: Sat, 18 May 2019 13:35:23 +0200 [thread overview]
Message-ID: <803b4a8b-573a-fc3d-b24e-92b0c1d1c8f2@ilbers.de> (raw)
In-Reply-To: <20190516125030.13190-1-claudius.heine.ext@siemens.com>
On 5/16/19 2:50 PM, claudius.heine.ext@siemens.com wrote:
> From: Claudius Heine <ch@denx.de>
>
> Hi,
>
> here is the fix for #56 without regression. Now its possible again to refer to
> the kernel and initrd names at any point in the image creation process, even if
> they were removed from the root fs in a cleanup step.
>
> regards,
> Claudius
Reworded and applied to the 'next'.
Maxim.
> Claudius Heine (2):
> image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed
> Revert "meta/classes/image: Call transform_template after
> rootfs_install"
>
> meta/classes/image.bbclass | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
--
Maxim Osipov
ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn
Germany
+49 (151) 6517 6917
mosipov@ilbers.de
http://ilbers.de/
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2019-05-18 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 12:50 claudius.heine.ext
2019-05-16 12:50 ` [PATCH 1/2] image.bbclass: make KERNEL_IMAGE & INITRD_IMAGE variable fixed claudius.heine.ext
2019-05-16 13:32 ` Claudius Heine
2019-05-16 12:50 ` [PATCH 2/2] Revert "meta/classes/image: Call transform_template after rootfs_install" claudius.heine.ext
2019-05-17 10:58 ` Maxim Yu. Osipov
2019-05-20 7:19 ` Claudius Heine
2019-05-20 19:47 ` Baurzhan Ismagulov
2019-05-21 8:06 ` Claudius Heine
2019-05-18 11:35 ` Maxim Yu. Osipov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=803b4a8b-573a-fc3d-b24e-92b0c1d1c8f2@ilbers.de \
--to=mosipov@ilbers.de \
--cc=ch@denx.de \
--cc=claudius.heine.ext@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox