From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: hs@denx.de, openembedded-core@lists.openembedded.org
Cc: Julius Werner <jwerner@chromium.org>
Subject: Re: [PATCH v2] kernel.fitimage.bbclass: remove ramdisk_ctype
Date: Mon, 18 Nov 2019 12:47:34 +0000 [thread overview]
Message-ID: <bdfd84b9e6a9171b4a8eb9b3e81e4f5b96f0b83f.camel@linuxfoundation.org> (raw)
In-Reply-To: <140626d6-0890-c2e1-0425-9e7e7a1a5fc3@denx.de>
On Mon, 2019-11-18 at 09:51 +0100, Heiko Schocher wrote:
> Hello all,
>
> Am 07.10.2019 um 15:42 schrieb Heiko Schocher:
> > Hello all,
> >
> > Am 20.09.2019 um 06:21 schrieb Heiko Schocher:
> > > set in the ramdisk node the compression property
> > > always to "none", as U-Boot nowadays since commit:
> > >
> > > b1307f884a91 ("fit: Support compression for non-kernel components
> > > (e.g. FDT)")
> > >
> > > decompress non kernel components. Setting compression
> > > to the used comression algorithm now, will end in
> > > fail of your kernel boot with the ramdisk.
> > >
> > > This issue is fixed since commit:
> > >
> > > bddd98573465 ("fit: Do not automatically decompress ramdisk
> > > images")
> > >
> > > which now prints a warning in U-Boot, instead of decompressing
> > > the ramdisk, but we should setup compression property correct.
> > >
> > > Signed-off-by: Heiko Schocher <hs@denx.de>
> > > ---
> > >
> > > Changes in v2:
> > > - resend patch to openembedded-core@lists.openembedded.org
> > > instead
> > > to Yocto Project <yocto@yoctoproject.org> as Ross suggested.
> > > No
> > > changes in code.
> >
> > gentle ping. Any comments?
>
> gentle ping ...
It merged 7 days after you sent it back in September:
http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=2c58079222310443f08df51e9fd6ce234e7e0019
Cheers,
Richard
next prev parent reply other threads:[~2019-11-18 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190920042112.14832-1-hs@denx.de>
2019-10-07 13:42 ` [PATCH v2] kernel.fitimage.bbclass: remove ramdisk_ctype Heiko Schocher
2019-11-18 8:51 ` Heiko Schocher
2019-11-18 12:47 ` Richard Purdie [this message]
2019-09-20 4:48 Heiko Schocher
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=bdfd84b9e6a9171b4a8eb9b3e81e4f5b96f0b83f.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=hs@denx.de \
--cc=jwerner@chromium.org \
--cc=openembedded-core@lists.openembedded.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.