Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
	Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/9] kernel: Clean up KERNEL_IMAGETYPE_FOR_MAKE
Date: Mon, 25 May 2015 03:33:30 +0200	[thread overview]
Message-ID: <201505250333.30333.marex@denx.de> (raw)
In-Reply-To: <5554BC2B.8070906@windriver.com>

On Thursday, May 14, 2015 at 05:15:55 PM, Bruce Ashfield wrote:
> The series looks good to me.
> 
> Acked-by: Bruce Ashfield <bruce.ashfield@windriver.com>

Hi,

any chance this could get applied so it can get further testing in-tree
please ?

Thank you!

Best regards,
Marek Vasut


  reply	other threads:[~2015-05-25  1:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 12:31 [PATCH 0/9] Add basic fitImage support Marek Vasut
2015-05-14 12:31 ` [PATCH 1/9] kernel: Clean up KERNEL_IMAGETYPE_FOR_MAKE Marek Vasut
2015-05-14 15:15   ` Bruce Ashfield
2015-05-25  1:33     ` Marek Vasut [this message]
2015-05-14 12:31 ` [PATCH 2/9] kernel: Rework do_uboot_mkimage Marek Vasut
2015-05-14 12:31 ` [PATCH 3/9] kernel: Pull out the linux.bin generation Marek Vasut
2015-05-14 12:31 ` [PATCH V2 4/9] kernel: Pull uImage generation into separate class Marek Vasut
2015-05-14 12:31 ` [PATCH 5/9] kernel: Separate out uboot_prep_kimage Marek Vasut
2015-05-14 12:31 ` [PATCH 6/9] kernel: Build DTBs early Marek Vasut
2015-05-14 12:31 ` [PATCH 7/9] kernel: Add basic fitImage support Marek Vasut
2015-05-14 12:31 ` [PATCH V2 8/9] kernel: Build uImage only when really needed Marek Vasut
2015-05-14 12:31 ` [PATCH 9/9] doc: Document new KERNEL_CLASSES variable 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=201505250333.30333.marex@denx.de \
    --to=marex@denx.de \
    --cc=bruce.ashfield@windriver.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox