From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Senthil Balasubramanian <senthilkumar@atheros.com>,
Senthilkumar Balasubramanian
<Senthilkumar.Balasubramanian@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Jiri Slaby <jirislaby@gmail.com>,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: [PATCH] wireless: convert reg_regdb_search_lock to mutex
Date: Wed, 17 Mar 2010 09:01:01 -0400 [thread overview]
Message-ID: <20100317130101.GB2990@tuxdriver.com> (raw)
In-Reply-To: <20100317125513.GA2990@tuxdriver.com>
On Wed, Mar 17, 2010 at 08:55:13AM -0400, John W. Linville wrote:
> On Tue, Mar 16, 2010 at 08:24:35PM -0700, Johannes Berg wrote:
> > English at work ... let me guess:
> >
> > For John: "can" == "it could happen that"
> > For Senthil: "can" == "may"
> >
> > (when really you may NOT do GFP_KERNEL allocations in atomic context)
>
> Ah, that seems like a plausible explanation for the confusion.
> Bitte mein herr!
Err...danke mein herr! :-)
John
--
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:[~2010-03-17 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 13:26 regd: sleeping in atomic Jiri Slaby
2010-03-16 16:18 ` Luis R. Rodriguez
2010-03-16 18:42 ` Jiri Slaby
2010-03-16 20:36 ` Luis R. Rodriguez
2010-03-16 19:49 ` [PATCH] wireless: convert reg_regdb_search_lock to mutex John W. Linville
2010-03-16 10:03 ` Senthil Balasubramanian
2010-03-17 0:24 ` John W. Linville
2010-03-16 12:24 ` Senthil Balasubramanian
2010-03-17 2:56 ` John W. Linville
2010-03-17 3:24 ` Johannes Berg
2010-03-17 1:26 ` Senthil Balasubramanian
2010-03-17 12:55 ` John W. Linville
2010-03-17 13:01 ` John W. Linville [this message]
2010-03-17 19:33 ` [PATCH v2] " John W. Linville
2010-03-18 20:47 ` [PATCH v3] " John W. Linville
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=20100317130101.GB2990@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Senthilkumar.Balasubramanian@Atheros.com \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=senthilkumar@atheros.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.