From: Vladimir Zapolskiy <vz@mleia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] NAND: remove remaining NAND_MAX_CHIPS definitions
Date: Tue, 06 Dec 2011 21:02:53 +0200 [thread overview]
Message-ID: <4EDE66DD.4030704@mleia.com> (raw)
In-Reply-To: <4EDE654A.20000@freescale.com>
On 06.12.2011 20:56, Scott Wood wrote:
> On 12/06/2011 12:34 PM, Vladimir Zapolskiy wrote:
>> On 06.12.2011 19:27, Scott Wood wrote:
>>> On 12/06/2011 07:58 AM, Vladimir Zapolskiy wrote:
>>>> Hi Scott,
>>>>
>>>> is there any problem with this pending change?
>>>
>>> No, looks good.
>>>
>> Being a NAND Flash custodian, would you like to pick it up?
>
> Yes, when I get to applying patches for the next merge window.
>
That's great, thank you a lot.
--
With best wishes,
Vladimir
prev parent reply other threads:[~2011-12-06 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-20 14:10 [U-Boot] [PATCH] NAND: remove remaining NAND_MAX_CHIPS definitions Vladimir Zapolskiy
2011-11-20 14:10 ` [U-Boot] [PATCH] NAND: remove " Vladimir Zapolskiy
2012-01-05 23:41 ` Scott Wood
2012-01-06 0:51 ` Marek Vasut
2011-12-06 13:58 ` [U-Boot] [PATCH] NAND: remove remaining " Vladimir Zapolskiy
2011-12-06 17:27 ` Scott Wood
2011-12-06 18:34 ` Vladimir Zapolskiy
2011-12-06 18:56 ` Scott Wood
2011-12-06 19:02 ` Vladimir Zapolskiy [this message]
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=4EDE66DD.4030704@mleia.com \
--to=vz@mleia.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