From: "Woodhouse, David" <david.woodhouse@intel.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: mxc-nand fix for 3.5 (Was: Re: [PATCH v2] mtd mxc_nand: use 32bit copy functions)
Date: Thu, 12 Jul 2012 07:28:10 +0000 [thread overview]
Message-ID: <1342078088.30654.14.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20120712065722.GA592@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
On Thu, 2012-07-12 at 08:57 +0200, Uwe Kleine-König wrote:
> The mxc_nand driver is completely useless with
>
> 5775ba3 (mtd: mxc_nand: fix several sparse warnings about incorrect address space)
>
> but without this patch. So it would be great if we could have it in 3.5.
> Or alternatively revert 5775ba3. This fix currently it sits as
>
> 096bcc2 (mtd: mxc_nand: use 32bit copy functions)
>
> in next/master.
The subject of that commit didn't jump out at me when I was perusing the
patch queue for 3.5-worthy stuff.
Artem reminded me about it just after I sent my previous pull request to
Linus last week. I wanted to let it sit in linux-next for a little
while, but now...
Linus, please pull from
git://git.infradead.org/linux-mtd.git for-linus-20120712
Late MTD fixes for 3.5:
- fix 'sparse warning fix' regression which totally breaks MXC NAND
- fix GPMI NAND regression when used with UBI
- update/correct sysfs documentation for new 'bitflip_threshold' field
- fix nandsim build failure
----
Herton Ronaldo Krzesinski (1):
mtd: nandsim: don't open code a do_div helper
Mike Dunn (1):
mtd: ABI documentation: clarification of bitflip_threshold
Sascha Hauer (2):
mtd: mxc_nand: use 32bit copy functions
mtd: gpmi-nand: fix read page when reading to vmalloced area
Documentation/ABI/testing/sysfs-class-mtd | 17 ++++++-------
drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 10 ++++----
drivers/mtd/nand/mxc_nand.c | 37 ++++++++++++++++++++++-------
drivers/mtd/nand/nandsim.c | 12 +++-------
4 files changed, 46 insertions(+), 30 deletions(-)
--
Sent with MeeGo's ActiveSync support.
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 4370 bytes --]
prev parent reply other threads:[~2012-07-12 7:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 8:16 [PATCH v2] mtd mxc_nand: use 32bit copy functions Sascha Hauer
2012-05-29 9:12 ` Uwe Kleine-König
2012-05-29 9:36 ` Sascha Hauer
2012-05-29 9:39 ` Russell King - ARM Linux
2012-05-29 9:47 ` Sascha Hauer
2012-06-29 11:46 ` Artem Bityutskiy
2012-07-12 6:57 ` mxc-nand fix for 3.5 (Was: Re: [PATCH v2] mtd mxc_nand: use 32bit copy functions) Uwe Kleine-König
2012-07-12 7:28 ` Woodhouse, David [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=1342078088.30654.14.camel@shinybook.infradead.org \
--to=david.woodhouse@intel.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=u.kleine-koenig@pengutronix.de \
/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