From: David.Woodhouse@intel.com (David Woodhouse)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2 v2] ARM: Fix gen_nand probe structures contents
Date: Thu, 12 Aug 2010 12:23:51 +0100 [thread overview]
Message-ID: <1281612232.12475.71.camel@localhost> (raw)
In-Reply-To: <1281581635-26213-1-git-send-email-marek.vasut@gmail.com>
On Thu, 2010-08-12 at 03:53 +0100, Marek Vasut wrote:
> These three platforms didn't properly fill nr_chips in gen_nand registration and
> therefore depended on gen_nand bug fixed by the following patch:
>
> "mtd: gen_nand: fix support for multiple chips"
>
> Signed-off-by: Marek Vasut <marek.vasut@gmail.com>
> ---
> v2: Added other broken boards outside arch-arm (mips and bfin)
> v1: Initial patch
>
> arch/arm/mach-ixp4xx/ixdp425-setup.c | 1 +
> arch/arm/mach-mx3/mach-qong.c | 1 +
> arch/arm/mach-orion5x/ts78xx-setup.c | 1 +
> arch/blackfin/mach-bf537/boards/stamp.c | 1 +
> arch/blackfin/mach-bf561/boards/acvilon.c | 1 +
> arch/mips/nxp/pnx833x/common/platform.c | 1 +
> 6 files changed, 6 insertions(+), 0 deletions(-)
I'd already applied the three in arch/arm. Have now applied the others;
thanks.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse at intel.com Intel Corporation
prev parent reply other threads:[~2010-08-12 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 2:53 [PATCH 1/2 v2] ARM: Fix gen_nand probe structures contents Marek Vasut
2010-08-12 2:53 ` [PATCH 2/2] gen_nand: Test if nr_chips field is valid Marek Vasut
2010-08-12 2:57 ` [PATCH 1/2 v2] ARM: Fix gen_nand probe structures contents Marek Vasut
2010-08-12 3:36 ` Mike Frysinger
2010-08-12 11:04 ` Marek Vasut
2010-08-12 12:47 ` Mike Frysinger
2010-08-12 13:48 ` Marek Vasut
2010-08-12 11:23 ` David Woodhouse [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=1281612232.12475.71.camel@localhost \
--to=david.woodhouse@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).