From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V3 1/4] README: document CONFIG_ENV_IS_IN_MMC
Date: Fri, 24 May 2013 09:47:41 -0600 [thread overview]
Message-ID: <519F8B9D.8040605@wwwdotorg.org> (raw)
In-Reply-To: <20130524152412.GO17119@bill-the-cat>
On 05/24/2013 09:24 AM, Tom Rini wrote:
> On Thu, May 23, 2013 at 02:51:44PM -0600, Stephen Warren wrote:
>
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Describe the meaning of CONFIG_ENV_IS_IN_MMC, and all related
>> defines that must or can be set when using that option.
>>
>> Signed-off-by: Stephen Warren <swarren@nvidia.com>
>
> Acked-by: Tom Rini <trini@ti.com>
TomR, I assume you want Andy Fleming to take this series through the
MMC tree?
TomW, if patch 4/4 is OK with you, can you ack it so that someone else
can take it, or do you want them to apply patches 1-3, wait until you
can pick them up in the Tegra tree, and then apply patch 4 yourself?
next prev parent reply other threads:[~2013-05-24 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 20:51 [U-Boot] [PATCH V3 1/4] README: document CONFIG_ENV_IS_IN_MMC Stephen Warren
2013-05-23 20:51 ` [U-Boot] [PATCH V3 2/4] mmc: report capacity for the selected partition Stephen Warren
2013-05-23 20:51 ` [U-Boot] [PATCH V3 3/4] env_mmc: allow negative CONFIG_ENV_OFFSET Stephen Warren
2013-05-23 20:51 ` [U-Boot] [PATCH V3 4/4] ARM: tegra: make use of negative ENV_OFFSET on NVIDIA boards Stephen Warren
2013-05-23 21:59 ` [U-Boot] [PATCH V3 1/4] README: document CONFIG_ENV_IS_IN_MMC Peter Korsgaard
2013-05-23 22:15 ` Stephen Warren
2013-05-23 22:32 ` Peter Korsgaard
2013-05-24 15:24 ` Tom Rini
2013-05-24 15:47 ` Stephen Warren [this message]
2013-05-24 15:51 ` Tom Rini
2013-05-24 16:03 ` Tom Warren
2013-06-04 19:31 ` Stephen Warren
2013-06-04 20:39 ` Fleming Andy-AFLEMING
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=519F8B9D.8040605@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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