From: Johannes Berg <johannes@sipsolutions.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: pmf_register_irq_client gives sleep with locks held warning
Date: Tue, 13 Jun 2006 10:43:19 +0200 [thread overview]
Message-ID: <1150188199.9208.7.camel@johannes> (raw)
In-Reply-To: <1149977097.12687.144.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
On Sun, 2006-06-11 at 08:04 +1000, Benjamin Herrenschmidt wrote:
> > That's ok, we don't have any in-kernel users anyway. Alas the alsa
> > people will be dissatisfied because they like to ship new drivers for
> > old kernels or something. Oh well, I don't care.
>
> We still want people to build out-of-tree for 2.6.17 (please keep the
> git there for that), as it will take a while before 2.6.18 is here.
Sure, I'll continue maintaining snd-aoa in that repository.
> The remaining possible bug in the pmf irq code is probably harmless in
> 99.99% of the cases in practice :)
I see your patch is in, I'll make a patch that fixes it then instead of
replacing it, I guess.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
next prev parent reply other threads:[~2006-06-13 8:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 20:19 pmf_register_irq_client gives sleep with locks held warning Johannes Berg
2006-06-01 0:59 ` Benjamin Herrenschmidt
2006-06-08 18:58 ` Johannes Berg
2006-06-10 0:03 ` Benjamin Herrenschmidt
2006-06-10 9:27 ` Johannes Berg
2006-06-10 22:04 ` Benjamin Herrenschmidt
2006-06-13 8:43 ` Johannes Berg [this message]
2006-06-13 9:58 ` Benjamin Herrenschmidt
2006-06-13 15:43 ` [PATCH] make pmf irq_client functions safe against pmf interrupts coming in Johannes Berg
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=1150188199.9208.7.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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).