From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: Missing patches for pxa3xx_nand
Date: Mon, 07 Nov 2011 12:27:00 +0100 [thread overview]
Message-ID: <4EB7C084.4060706@gmail.com> (raw)
Hi,
In June, there have been important patches submitted for the pxa3xx_nand
driver after it was broken by Lei's rework series. These patches were
discussed in June, and they are present in
git://git.infradead.org/mtd-2.6.git linux-fallback
but not in the master branch of the same git. Also, they have not been
merged to Linus' master tree which renders the pxa3xx_nand driver
unusable in 3.0 and 3.1.
A selection of the patches I'm talking about are titled
mtd: pxa3xx_nand: Fix blank page ECC mismatch
mtd: pxa3xx_nand: fix nand detection issue
mtd: pxa3xx_nand don't specify default parsing options
and of course they depend on others that aren't merged yet either.
Can anyone explain what went wrong here and how we can get out of this?
Thanks,
Daniel
next reply other threads:[~2011-11-07 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 11:27 Daniel Mack [this message]
2011-11-07 11:37 ` Missing patches for pxa3xx_nand Daniel Mack
2011-11-17 21:13 ` Artem Bityutskiy
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=4EB7C084.4060706@gmail.com \
--to=zonque@gmail.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).