From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 2/4] ARM: mvebu: drivers for v3.9
Date: Sun, 13 Jan 2013 01:05:35 +0000 [thread overview]
Message-ID: <20130113010535.GR23505@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <E1TuAWu-0004Jx-Hn@merlin.infradead.org>
On Sat, Jan 12, 2013 at 11:29:16PM +0000, Jason Cooper wrote:
> Thomas Petazzoni (4):
> mmc: mvsdio: use slot-gpio infrastructure for write protect gpio
> mmc: mvsdio: use slot-gpio for card detect gpio
> mmc: mvsdio: implement a Device Tree binding
> mmc: mvsdio: add pinctrl integration
Does this include the fixes for the really broken stuff in that driver?
If not, hold off on this until it's fixed. The current state of the
driver is rather BROKEN and it needs fixing in -rc. It would be best
to get it fixed there _then_ base development on top of that to avoid
conflicts.
next prev parent reply other threads:[~2013-01-13 1:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 23:29 [GIT PULL 0/4] ARM: mvebu: changes for v3.9 Jason Cooper
2013-01-12 23:29 ` [GIT PULL 1/4] ARM: mvebu: cleanup " Jason Cooper
2013-01-12 23:29 ` [GIT PULL 2/4] ARM: mvebu: drivers " Jason Cooper
2013-01-12 23:29 ` [GIT PULL 3/4] ARM: mvebu: boards " Jason Cooper
2013-01-12 23:29 ` [GIT PULL 4/4] ARM: mvebu: dt " Jason Cooper
[not found] ` <E1TuAWu-0004Jx-Hn@merlin.infradead.org>
2013-01-13 1:05 ` Russell King - ARM Linux [this message]
2013-01-13 1:28 ` [GIT PULL 2/4] ARM: mvebu: drivers " Jason Cooper
[not found] ` <E1TuAWD-0004Ec-1G@merlin.infradead.org>
2013-01-13 1:06 ` [GIT PULL 3/4] ARM: mvebu: boards " Russell King - ARM Linux
[not found] ` <E1TuAWi-0004H4-K6@merlin.infradead.org>
2013-01-13 1:06 ` [GIT PULL 4/4] ARM: mvebu: dt " Russell King - ARM Linux
2013-01-13 1:30 ` Jason Cooper
2013-01-23 2:48 ` [GIT PULL V2 0/4] ARM: mvebu: changes " Jason Cooper
2013-01-23 2:48 ` [GIT PULL V2 1/4] ARM: mvebu: cleanup " Jason Cooper
2013-01-28 5:57 ` Olof Johansson
2013-01-23 2:48 ` [GIT PULL V2 2/4] ARM: mvebu: drivers " Jason Cooper
2013-01-28 5:53 ` Olof Johansson
2013-01-28 11:53 ` Chris Ball
2013-01-28 16:10 ` Jason Cooper
2013-01-23 2:48 ` [GIT PULL V2 3/4] ARM: mvebu: boards " Jason Cooper
2013-01-23 2:48 ` [GIT PULL V2 4/4] ARM: mvebu: dt " Jason Cooper
-- strict thread matches above, loose matches on Subject: below --
2013-02-01 15:51 [GIT PULL 0/4] ARM: mvebu: changes " Jason Cooper
2013-02-01 15:51 ` [GIT PULL 2/4] ARM: mvebu: drivers " Jason Cooper
2013-02-05 7:10 ` Olof Johansson
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=20130113010535.GR23505@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).