From: "John W. Linville" <linville@tuxdriver.com>
To: Solomon Peachy <pizza@shaftnet.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/2] cw1200: Don't perform SPI transfers in interrupt context
Date: Mon, 9 Sep 2013 14:33:50 -0400 [thread overview]
Message-ID: <20130909183350.GB1955@tuxdriver.com> (raw)
In-Reply-To: <20130903115856.GA16844@shaftnet.org>
On Tue, Sep 03, 2013 at 07:58:57AM -0400, Solomon Peachy wrote:
> On Tue, Aug 27, 2013 at 08:29:46PM -0400, Solomon Peachy wrote:
> > When we get an interrupt from the hardware, the first thing the driver does
> > is tell the device to mask off the interrupt line. Unfortunately this
> > involves a SPI transaction in interrupt context. Some (most?) SPI
> > controllers perform the transfer asynchronously and try to sleep.
> > This is bad, and triggers a BUG().
>
> Did this patch series get dropped? I saw that the followup series
> of minor cleanups were merged into wireless-next, but not these.
>
> Since they didn't make it into 3.11, I intend to submit them to -stable,
> but I need to make sure they at least make it into -next.
I'll be sending them for 3.12 soon...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2013-09-09 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 0:29 [PATCH 1/2] cw1200: Don't perform SPI transfers in interrupt context Solomon Peachy
2013-08-28 0:29 ` [PATCH 2/2] cw1200: Prevent a lock-related hang in the cw1200_spi driver Solomon Peachy
2013-09-03 11:58 ` [PATCH 1/2] cw1200: Don't perform SPI transfers in interrupt context Solomon Peachy
2013-09-09 18:33 ` John W. Linville [this message]
2013-09-14 2:47 ` Solomon Peachy
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=20130909183350.GB1955@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=linux-wireless@vger.kernel.org \
--cc=pizza@shaftnet.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