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 resend] mpc5121_nfc: Changed SVR check to allow MPC5123.
Date: Thu, 06 May 2010 09:42:07 +0300 [thread overview]
Message-ID: <1273128127.3702.201.camel@localhost> (raw)
In-Reply-To: <181804936ABC2349BE503168465576460EA16F75@exchserver.basler.com>
On Wed, 2010-05-05 at 13:48 -0500, Steve Deiters wrote:
> The revision in SVR for MPC5123 is 3. The NFC is the same as MPC5121
> revision 2.
>
> Signed-off-by: Steve Deiters <SteveDeiters@basler.com>
> ---
> drivers/mtd/nand/mpc5121_nfc.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/nand/mpc5121_nfc.c
> b/drivers/mtd/nand/mpc5121_nfc.c
> index 191bf99..dc04d74 100644
> --- a/drivers/mtd/nand/mpc5121_nfc.c
> +++ b/drivers/mtd/nand/mpc5121_nfc.c
> @@ -666,10 +666,10 @@ static int __devinit mpc5121_nfc_probe(struct
> of_device *op,
>
> /*
> * Check SoC revision. This driver supports only NFC
> - * in MPC5121 revision 2.
> + * in MPC5121 revision 2 and MPC5123 revision 3.
> */
> rev = (mfspr(SPRN_SVR) >> 4) & 0xF;
> - if (rev != 2) {
> + if ((rev != 2) && (rev != 3)) {
> dev_err(dev, "SoC revision %u is not supported!\n",
> rev);
> return -ENXIO;
> }
Now your patch is line-wrapped. But I fixed it and pushed to
l2-mtd-2.6.git / master.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-05-06 6:43 UTC|newest]
Thread overview: 6+ 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-04-28 22:33 ` Steve Deiters
2010-05-04 13:47 ` Artem Bityutskiy
2010-05-05 18:48 ` [PATCH resend] " Steve Deiters
2010-05-05 18:48 ` Steve Deiters
2010-05-06 6:42 ` Artem Bityutskiy [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=1273128127.3702.201.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.