From: Samuel Ortiz <sameo@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: linux-kernel@vger.kernel.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] mfd: Acknowlege all WM831x IRQs before we handle them
Date: Wed, 27 Jul 2011 11:52:40 +0200 [thread overview]
Message-ID: <20110727095240.GA26275@sortiz-mobl> (raw)
In-Reply-To: <1311177913-4560-1-git-send-email-broonie@opensource.wolfsonmicro.com>
Hi Mark,
On Wed, Jul 20, 2011 at 05:05:13PM +0100, Mark Brown wrote:
> Ensure that we never have a window where we've handled an interrupt (and
> therefore need to be notified of new events) but haven't yet told the
> interrupt controller that this is the case (so any new events will be
> discarded).
Thanks, patch applied.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
prev parent reply other threads:[~2011-07-27 9:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 16:05 [PATCH] mfd: Acknowlege all WM831x IRQs before we handle them Mark Brown
2011-07-27 9:52 ` Samuel Ortiz [this message]
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=20110727095240.GA26275@sortiz-mobl \
--to=sameo@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.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