From: Bartlomiej Sieka <tur@semihalf.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] [new uImage] rework error handling so common functions don't reset
Date: Fri, 22 Feb 2008 15:36:09 +0100 [thread overview]
Message-ID: <47BEDDD9.1080007@semihalf.com> (raw)
In-Reply-To: <20080222115000.3517F243AB@gemini.denx.de>
Wolfgang Denk wrote:
> Dear Kumar,
>
> in message <Pine.LNX.4.64.0802181306060.21964@blarg.am.freescale.net> you wrote:
>> Changed image_get_ramdisk() to just return NULL on error and have
>> get_ramdisk() propogate that error to the caller. It's left to the
>> caller to call do_reset() if it wants to.
>>
>> Also moved calling do_reset() in get_fdt() on ppc to a common location.
>> In the future we will change get_fdt() to return success/failure and
>> not call do_reset() at all.
>>
>> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
>
> Just to make my position clear: I expect that you negotiate new-image
> related patches more or less directly with Bartek, who I consider as
> kind of "new-image" custodian.
>
> That means that I will not track the state of these patches - if you
> want me to apply something directly, please ring a bell.
>
> Bartek: I would also appreciate if you could merge Kumar's patches in
> a local repo and then send me just a pull request when something is
> ready to go into u-boot-testing (or even into mainline).
OK, will coordinate new uImage stuff that gets posted to the list, and
request pulling as needed.
Regards,
Bartlomiej
next prev parent reply other threads:[~2008-02-22 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 19:06 [U-Boot-Users] [PATCH] [new uImage] rework error handling so common functions don't reset Kumar Gala
2008-02-22 11:50 ` Wolfgang Denk
2008-02-22 14:36 ` Bartlomiej Sieka [this message]
2008-02-26 5:52 ` 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=47BEDDD9.1080007@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox