From: Marek Vasut <marex@denx.de>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] Add initial fitImage support
Date: Thu, 7 Aug 2014 22:15:33 +0200 [thread overview]
Message-ID: <201408072215.33862.marex@denx.de> (raw)
In-Reply-To: <53E3DD34.4000100@linux.intel.com>
On Thursday, August 07, 2014 at 10:10:28 PM, Saul Wold wrote:
> On 08/07/2014 08:17 AM, Marek Vasut wrote:
> > The fitImage is a successor of the U-Boot uImage format, which is
> > considered legacy for years now. The fitImage allows packing multiple
> > kernel images, DTBs and other artifacts into a single image, which can
> > then be protected by SHA checksums and does even support signing the
> > images for verified boot.
> >
> > This patchset is the first stab at adding the new image format into
> > Yocto.
> >
> > Marek Vasut (5):
> > Yocto: kernel: Rework do_uboot_mkimage
> > Yocto: kernel: Pull out the linux.bin generation
> > Yocto: kernel: Clean up KERNEL_IMAGETYPE_FOR_MAKE
> > Yocto: kernel: Build DTBs early
> > Yocto: kernel: Add basic fitImage support
> >
> > meta/classes/kernel.bbclass | 229
> > +++++++++++++++++++++++++++++---
> > meta/recipes-kernel/linux/linux-dtb.inc | 14 +-
> > 2 files changed, 226 insertions(+), 17 deletions(-)
>
> Hi Marek,
>
> I am going to make a general request, can you please review the Commit
> Guildlines Wiki for Openembedded:
>
> http://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
>
> We appreciate your patches, but the commit messages need to be formatted
> correctly. The Yocto: tag is not needed and you could clearly include
> which recipe, bbclass, file or subsystem (if across multiple files) so
> in the above it would be kernel.bbclass: ...
>
> If you could please resubmit your changes with the correct commit
> summary for this series and your other patches that would be greatly
> appreciated.
>
> Myself and others may have further feedback on your patches.
Ah, thanks! I'll give it a few days and will do V2 as per guidelines. Sorry for
the mistake.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-08-07 20:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 15:17 [PATCH 0/5] Add initial fitImage support Marek Vasut
2014-08-07 15:17 ` [PATCH 2/5] Yocto: kernel: Pull out the linux.bin generation Marek Vasut
2014-08-07 15:17 ` [PATCH 3/5] Yocto: kernel: Clean up KERNEL_IMAGETYPE_FOR_MAKE Marek Vasut
2014-08-07 15:17 ` [PATCH 5/5] Yocto: kernel: Add basic fitImage support Marek Vasut
2014-08-11 0:55 ` Otavio Salvador
2014-08-07 20:10 ` [PATCH 0/5] Add initial " Saul Wold
2014-08-07 20:15 ` Marek Vasut [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-07 15:26 Marek Vasut
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=201408072215.33862.marex@denx.de \
--to=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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 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.