From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mmci: fixup broken_blockend variant patch v2
Date: Sun, 23 Jan 2011 18:01:10 +0000 [thread overview]
Message-ID: <20110123180110.GJ30094@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <AANLkTim4i8BibVFmn2C4ixRoMrX5mNU9HZjW2KGMXsYZ@mail.gmail.com>
On Fri, Jan 21, 2011 at 01:53:06PM +0100, Linus Walleij wrote:
> This means that I think the patch I've sent should be the way
> forward.
Which particular patch - there seems to be soo many fiddling with
the various broken flags and so forth.
If we're going to move away from the blockend IRQs to using the data
counter, can we have a patch which switches the driver to use the data
counter and then a followup patch which removes the broken blockend
stuff, rather than somethign that changes the broken blockend stuff
and then removes it?
next prev parent reply other threads:[~2011-01-23 18:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 14:37 [PATCH] mmci: fixup broken_blockend variant patch v2 Linus Walleij
2011-01-17 15:12 ` Rabin Vincent
2011-01-17 16:02 ` Linus Walleij
2011-01-18 12:14 ` Russell King - ARM Linux
2011-01-19 20:34 ` Linus Walleij
2011-01-19 20:51 ` Russell King - ARM Linux
2011-01-19 23:52 ` Linus Walleij
2011-01-21 12:53 ` Linus Walleij
2011-01-23 18:01 ` Russell King - ARM Linux [this message]
2011-01-23 21:40 ` Linus Walleij
2011-01-23 23:09 ` Russell King - ARM Linux
2011-01-24 8:18 ` Linus Walleij
2011-01-24 11:21 ` Russell King - ARM Linux
2011-01-24 14:29 ` Linus Walleij
2011-01-27 11:06 ` Russell King - ARM Linux
2011-01-27 14:16 ` Linus Walleij
2011-01-17 15:36 ` Rabin Vincent
2011-01-17 15:56 ` Linus Walleij
2011-01-17 16:56 ` Rabin Vincent
2011-01-18 15:01 ` Linus Walleij
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=20110123180110.GJ30094@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).