From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mfd: Convert WM8350 to use request_threaded_irq()
Date: Thu, 17 Sep 2009 10:33:04 +0100 [thread overview]
Message-ID: <20090917093304.GA30736@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20090917090155.GB18862@sortiz.org>
On Thu, Sep 17, 2009 at 11:01:56AM +0200, Samuel Ortiz wrote:
> On Wed, Sep 16, 2009 at 07:07:32PM +0100, Mark Brown wrote:
> > Instead of hand rolling our own variant.
> Very nice. I expect many other mfd drivers will eventually go the same way.
> I'll look at the ones I have HW for.
I've got a patch sitting waiting to convert wm831x completely to genirq,
including changing to use threaded IRQ handlers. It'll probably be
after the merge window before I finish up testing and post it.
next prev parent reply other threads:[~2009-09-17 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 18:07 [PATCH] mfd: Convert WM8350 to use request_threaded_irq() Mark Brown
2009-09-17 9:01 ` Samuel Ortiz
2009-09-17 9:33 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-16 17:44 Mark Brown
2009-09-16 18:06 ` Mark Brown
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=20090917093304.GA30736@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
/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