From: Tom Rini <trini@ti.com>
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 11:51:25 -0400 [thread overview]
Message-ID: <519F8C7D.8030201@ti.com> (raw)
In-Reply-To: <519F8B9D.8040605@wwwdotorg.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 05/24/2013 11:47 AM, Stephen Warren wrote:
> 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?
Correct, and I've given these to Andy in patchwork as well. Thanks!
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJRn4x8AAoJENk4IS6UOR1WjnQP/3wZXbkkM+EzxbQXQUV2n5gY
aQa5qUAKrZHJ5YyNhjuewoZV0zzSkPYeb3BXeKKGJWc7mZ1ZEBb9ffqBrY88LVa+
BnFEGLDjM7pHRuuDk4nLsXdMhP18O0kJC3QyNh5Js4b3AH3WwMs8tvAyH854+Zh0
xAXx04y6flMyL+ZiaNA1v95I0U52hxqOsUazGqP7Cm0poHahIMN3WdiHefcebLRb
vsyGr1cVdGjAl4vc7fGmeWqwvKTKE/9a/usDujf0eVmVjkpNioT9FYmiGZC3SlEV
bI1YpgNkNSEjj2DlkiCUIly0JHaUX3KgDypEmPS4i/qGAk6EpLlmalZrcZD1+Md+
xZ+aaIQVg6d9ixzBJ0RraXLdil6Gkp3DkwQdz0IjdBBmxWaTelN1iCSwmmaYl544
MXaZ8ptF7qubKMvqYYQ7IqOV9eZ18UQ5vhrQ4OLmLDQPhoi+3Hzq/7X9gXn1c4t9
SB6+B4G6LqtCebSAzhwTVLL5SaA0SbJC8fyFSb1e/SaTeal3+0DGQAUKLN7+XNoo
B+uXLXGdzQuI3I0kF+z9l4MLD2vO/4sOu7ib9KsV2Z3Hz+Onfs+Oq/2QsYinzClT
C3lMMCgzoJCSv3K9UcaOj2z6KHQFy76Xq1eUhMmh0Arg/th4vzFXfboJpXTzwqv7
TxT5m9kyPEjOONVGPLDe
=Eoa+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-05-24 15:51 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
2013-05-24 15:51 ` Tom Rini [this message]
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=519F8C7D.8030201@ti.com \
--to=trini@ti.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