Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: jkosina@suse.cz (Jiri Kosina)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [TRIVIAL] ARM: imx: Fix typo 'MACH_MX31_3DS_MXC_NAND_USE_BBT'
Date: Wed, 2 Nov 2011 14:34:00 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.00.1111021433220.348@pobox.suse.cz> (raw)
In-Reply-To: <CAOMZO5DZ6KYa_SLVavorPPyV_Ggspa4Cae+eK7oj1mh=O4J4+w@mail.gmail.com>

On Tue, 1 Nov 2011, Fabio Estevam wrote:

> >> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> >> ---
> >> This is trivial because this is what apparently was intended. On the
> >> other hand this should open code paths that were hidden until now. So
> >> perhaps this needs the maintainer's approval. (I cannot meaningfully
> >> test this.)
> >
> > I'd like to have this tested by some relevant people before taking it
> > myself (added some CCs).
> 
> On a mx31pdk board I get the following with this patch applied and
> CONFIG_MACH_MX31_3DS_MXC_NAND_USE_BBT selected:
> 
> NAND device: Manufacturer ID: 0xec, Chip ID: 0xaa (Samsung NAND 256MiB
> 1,8V 8-bit)
> Bad block table not found for chip 0
> Bad block table not found for chip 0
> Scanning device for bad blocks
> Registering mxc_nand as whole device
> 
> Tested-by: Fabio Estevam <fabio.estevam@freescale.com>

Thank you, I will be appplying it.

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2011-11-02 13:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 12:04 [PATCH] [TRIVIAL] ARM: imx: Fix typo 'MACH_MX31_3DS_MXC_NAND_USE_BBT' Paul Bolle
2011-10-31 10:12 ` Jiri Kosina
2011-11-01 18:19   ` Fabio Estevam
2011-11-02 13:34     ` Jiri Kosina [this message]
2011-11-02 13:43       ` Paul Bolle

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=alpine.LNX.2.00.1111021433220.348@pobox.suse.cz \
    --to=jkosina@suse.cz \
    --cc=linux-arm-kernel@lists.infradead.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