From: Bartlomiej Sieka <tur@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH v2] [new uImage] ppc: Re-order ramdisk/fdt handling sequence
Date: Fri, 22 Feb 2008 15:36:53 +0100 [thread overview]
Message-ID: <47BEDE05.7060008@semihalf.com> (raw)
In-Reply-To: <47BECDA9.3010103@ge.com>
Jerry Van Baren wrote:
> Wolfgang Denk wrote:
>> In message <8B11A571-3BC2-42BD-9B66-DF22A736A3A7@kernel.crashing.org> you wrote:
>>> And the whole point of my patch was to enable the ability to
>>> dynamically grow the blob before we do anything w/the ramdisk.
>> So what is the state of this patch now? Will it go in through the FDT
>> custodian repo, or has it been rejected, or am I supposed to apply it
>> directly? Or?
[...]
> Most of the email exchanges were with me and the patch is fine IMHO.
>
> I was expecting it to go through the "new-image" custodian, but I would
> be happy to apply it to the u-boot-fdt repo and push it up from there.
Jerry, Kumar,
I think it would be better to have this patch (and other ones by Kumar
that touch booting-related code) go through the new-image branch.
Otherwise we'll have merge conflicts down the road, especially since
we've got a big patch coming, that adds framework for new image
handling. I'd like to have this framework patch merged first, then take
care of (re-based) boot-related patches that have been posted recently.
Regards,
Bartlomiej
next prev parent reply other threads:[~2008-02-22 14:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 17:27 [U-Boot-Users] [PATCH v2] [new uImage] ppc: Re-order ramdisk/fdt handling sequence Kumar Gala
2008-02-18 17:51 ` Jerry Van Baren
2008-02-18 18:52 ` Kumar Gala
2008-02-18 19:15 ` Jerry Van Baren
2008-02-18 19:39 ` Kumar Gala
2008-02-18 19:46 ` Jerry Van Baren
2008-02-18 20:13 ` Kumar Gala
2008-02-22 11:43 ` Wolfgang Denk
2008-02-22 13:27 ` Jerry Van Baren
2008-02-22 14:36 ` Bartlomiej Sieka [this message]
2008-02-26 5:48 ` Kumar Gala
2008-02-22 15:32 ` Marian Balakowicz
2008-02-22 15:53 ` Marian Balakowicz
2008-02-22 16:07 ` Jerry Van Baren
2008-02-22 17:08 ` Marian Balakowicz
2008-02-26 5:52 ` Kumar Gala
2008-02-26 9:11 ` Marian Balakowicz
2008-02-26 14:31 ` Kumar Gala
2008-02-27 11:20 ` Marian Balakowicz
2008-02-27 14:58 ` Kumar Gala
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=47BEDE05.7060008@semihalf.com \
--to=tur@semihalf.com \
--cc=u-boot@lists.denx.de \
/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.