From: Michael Trimarchi <trimarchi@gandalf.sssup.it>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2] This patch fix the usage of the "CE don't care"-type NAND chips
Date: Wed, 23 Feb 2011 13:10:15 +0100 [thread overview]
Message-ID: <4D64F927.1000200@gandalf.sssup.it> (raw)
In-Reply-To: <4D64F2A0.9030906@free.fr>
Hi,
On 02/23/2011 12:42 PM, Albert ARIBAUD wrote:
> Hi Michael,
>
> Le 23/02/2011 12:28, Michael Trimarchi a ?crit :
>> Change since V1:
>>
>> - add a better description
>
> History should not be put above the '---' cut line; it should be below.
>
>> Signed-off-by: Michael Trimarchi<michael@evidence.eu.com>
>> Cc: Scott Wood<scottwood@freescale.com>
>> ---
>> drivers/mtd/nand/atmel_nand.c | 10 ++++++++++
>> 1 files changed, 10 insertions(+), 0 deletions(-)
>> [...]
>
I will edit the text and resend with mutt. do I need to change again revision?
Michael Trimarchi
> Amicalement,
next prev parent reply other threads:[~2011-02-23 12:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 11:28 [U-Boot] [PATCH V2] This patch fix the usage of the "CE don't care"-type NAND chips Michael Trimarchi
2011-02-23 11:42 ` Albert ARIBAUD
2011-02-23 12:10 ` Michael Trimarchi [this message]
2011-02-23 12:46 ` Wolfgang Denk
2011-02-23 16:32 ` Scott Wood
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=4D64F927.1000200@gandalf.sssup.it \
--to=trimarchi@gandalf.sssup.it \
--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