linux-kernel - Re: [PATCH] [TRIVIAL] ARM: imx: Fix typo 'MACH_MX31_3DS_MXC_NAND_USE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 2 Nov 2011 14:34:00 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Fabio Estevam <festevam@...il.com>
Cc:	Paul Bolle <pebolle@...cali.nl>,
	Fabio Estevam <fabio.estevam@...escale.com>,
	Russell King <linux@....linux.org.uk>,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	Uwe Kleine-König 
	<u.kleine-koenig@...gutronix.de>
Subject: Re: [PATCH] [TRIVIAL] ARM: imx: Fix typo
 'MACH_MX31_3DS_MXC_NAND_USE_BBT'

On Tue, 1 Nov 2011, Fabio Estevam wrote:

> >> Signed-off-by: Paul Bolle <pebolle@...cali.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@...escale.com>

Thank you, I will be appplying it.

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/