From: ezequiel.garcia@free-electrons.com (Ezequiel Garcia)
To: linux-arm-kernel@lists.infradead.org
Subject: Merge order in Armada 370/XP (mvebu) NAND support
Date: Fri, 6 Dec 2013 15:45:45 -0300 [thread overview]
Message-ID: <20131206184544.GA14986@localhost> (raw)
Hello,
Now that all the pxa3xx-nand code has been merged by proper maintainers
and is available in each subsystem's trees I'd like to ask for suggestions
regarding a potential problem.
Since v3.12, the pxa3xx-nand driver supports the "armada370-nand"
compatible. This was probably a mistake as little to no NAND support
is present in that release.
The support to handle 4K pages devices (for instance, supporting the Mirabox
board) was submitted later, and is currently in MTD tree, waiting to be
pulled in v3.14.
On the other side, the devicetree files (dts and dtsi) needed to enable
such support was taken through the mvebu tree. Currently, a board booted
using mvebu's for-next branch will try to probe the NAND device
(because the compatible was merged in v3.12) and there's a chance it
hits on of NAND core's BUG().
The patchset containing the devicetree changes was prepared under the
assumption that the driver would be merged first, so no risk existed.
I admit this was a crappy assumption on my side to make (and worse:
it's not the first time I assume this).
Jason/Brian: What do you think we can do?
--
Ezequiel Garc?a, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next reply other threads:[~2013-12-06 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-06 18:45 Ezequiel Garcia [this message]
2013-12-06 19:25 ` Merge order in Armada 370/XP (mvebu) NAND support Jason Cooper
2013-12-06 22:12 ` Ezequiel Garcia
2013-12-09 19:08 ` Brian Norris
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=20131206184544.GA14986@localhost \
--to=ezequiel.garcia@free-electrons.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).