From: Artem Bityutskiy <dedekind1@gmail.com>
To: Steve Deiters <SteveDeiters@BASLER.com>
Cc: linuxppc-dev@lists.ozlabs.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mpc5121_nfc: Changed SVR check to allow MPC5123.
Date: Tue, 04 May 2010 16:47:43 +0300 [thread overview]
Message-ID: <1272980863.3702.10.camel@localhost> (raw)
In-Reply-To: <181804936ABC2349BE503168465576460E95836C@exchserver.basler.com>
On Wed, 2010-04-28 at 17:33 -0500, Steve Deiters wrote:
> The revision in SVR for MPC5123 is 3. The NFC is the same as MPC5121
> revision 2.
>
> ---
> drivers/mtd/nand/mpc5121_nfc.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
Please, add your Signed-off-by and re-send.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-05-04 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 22:33 [PATCH] mpc5121_nfc: Changed SVR check to allow MPC5123 Steve Deiters
2010-05-04 13:47 ` Artem Bityutskiy [this message]
2010-05-05 18:48 ` [PATCH resend] " Steve Deiters
2010-05-06 6:42 ` Artem Bityutskiy
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=1272980863.3702.10.camel@localhost \
--to=dedekind1@gmail.com \
--cc=SteveDeiters@BASLER.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).