From: Arjan van de Ven <arjan@linux.intel.com>
To: Valdis.Kletnieks@vt.edu
Cc: Rusty Russell <rusty@rustcorp.com.au>, linux-kernel@vger.kernel.org
Subject: Re: linux-next - request_module_nowait() breaks iptables and iwl3945
Date: Mon, 16 Mar 2009 08:37:47 -0700 [thread overview]
Message-ID: <49BE724B.80902@linux.intel.com> (raw)
In-Reply-To: <3823.1237168684@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
> On recent linux-next, iptables and iwl3945 would fail to load
>
> Bisected down to this commit:
>
this is ... curious. I just looked at the patch again and it really
looks like it really does not impact the existing codepaths...
do you have any more diagnostics other than "they do not work" ?
next prev parent reply other threads:[~2009-03-16 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-16 1:58 linux-next - request_module_nowait() breaks iptables and iwl3945 Valdis.Kletnieks
2009-03-16 15:37 ` Arjan van de Ven [this message]
2009-03-17 5:57 ` Rusty Russell
2009-03-17 22:27 ` Valdis.Kletnieks
2009-03-18 4:12 ` Rusty Russell
2009-03-18 4:59 ` Arjan van de Ven
2009-03-18 23:39 ` Rusty Russell
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=49BE724B.80902@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
/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