From: marek.vasut@gmail.com (Marek Vasut)
To: linux-arm-kernel@lists.infradead.org
Subject: zImage and raw ramdisk support -- test
Date: Fri, 30 Mar 2012 17:38:57 +0200 [thread overview]
Message-ID: <201203301738.57972.marek.vasut@gmail.com> (raw)
Guys,
I need final test on as much platforms as possible. Can you please run these two
following patches and tell me if they work with zImage and raw ramdisk for you?
http://patchwork.ozlabs.org/patch/146848/
http://patchwork.ozlabs.org/patch/147440/
I can't promise they will make it to this release (I've been pestering WD pretty
thoroughly (sorry about that), though I'm starting to be unhappy to merge this
stuff at the verge of release myself).
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] zImage and raw ramdisk support -- test
Date: Fri, 30 Mar 2012 17:38:57 +0200 [thread overview]
Message-ID: <201203301738.57972.marek.vasut@gmail.com> (raw)
Guys,
I need final test on as much platforms as possible. Can you please run these two
following patches and tell me if they work with zImage and raw ramdisk for you?
http://patchwork.ozlabs.org/patch/146848/
http://patchwork.ozlabs.org/patch/147440/
I can't promise they will make it to this release (I've been pestering WD pretty
thoroughly (sorry about that), though I'm starting to be unhappy to merge this
stuff at the verge of release myself).
Best regards,
Marek Vasut
next reply other threads:[~2012-03-30 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 15:38 Marek Vasut [this message]
2012-03-30 15:38 ` [U-Boot] zImage and raw ramdisk support -- test Marek Vasut
2012-03-30 19:30 ` Robert Nelson
2012-03-30 19:30 ` Robert Nelson
2012-03-30 20:24 ` Marek Vasut
2012-03-30 20:24 ` Marek Vasut
2012-03-30 21:38 ` Wolfgang Denk
2012-03-30 21:38 ` Wolfgang Denk
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=201203301738.57972.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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.