From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: mxc-nand fix for 3.5 (Was: Re: [PATCH v2] mtd mxc_nand: use 32bit copy functions)
Date: Thu, 12 Jul 2012 08:57:22 +0200 [thread overview]
Message-ID: <20120712065722.GA592@pengutronix.de> (raw)
In-Reply-To: <1340970369.3070.166.camel@sauron.fi.intel.com>
On Fri, Jun 29, 2012 at 02:46:09PM +0300, Artem Bityutskiy wrote:
> On Tue, 2012-05-29 at 10:16 +0200, Sascha Hauer wrote:
> > The following commit changes the function used to copy from/to
> > the hardware buffer to memcpy_[from|to]io. This does not work
> > since the hardware cannot handle the byte accesses used by these
> > functions. Instead of reverting this patch introduce 32bit
> > correspondents of these functions.
>
> Pushed to l2-mtd.git, thanks!
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.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2012-07-12 6:57 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 ` Uwe Kleine-König [this message]
2012-07-12 7:28 ` mxc-nand fix for 3.5 (Was: Re: [PATCH v2] mtd mxc_nand: use 32bit copy functions) Woodhouse, David
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=20120712065722.GA592@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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).