From: "John W. Linville" <linville@tuxdriver.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Wu <flamingice@sourmilk.net>,
Johannes Berg <johannes@sipsolutions.net>,
Jiri Benc <jbenc@suse.cz>
Subject: Re: [PATCH 1/2] mac80211: fix recursive locking in ieee80211_sta_expire
Date: Tue, 8 Apr 2008 19:43:21 -0400 [thread overview]
Message-ID: <20080408234321.GB23670@tuxdriver.com> (raw)
In-Reply-To: <47FBEC4B.7030205@gmail.com>
On Wed, Apr 09, 2008 at 12:06:03AM +0200, Jiri Slaby wrote:
> On 04/08/2008 08:35 PM, John W. Linville wrote:
>> On Mon, Apr 07, 2008 at 09:53:48PM +0200, Jiri Slaby wrote:
>>> Hi,
>>>
>>> it's against -mm, what's current mac80211 git tree? It seems that
>>> -mm has fresher material, than wireless-2.6...
>>
>> As it should. The wireless-2.6 tree is for feeding the linux-2.6 tree
>> (by way of the net-2.6 tree). Similarly, wireless-2.6.26 feeds -mm
>> by way of the net-2.6.26 tree.
>
> Wow, too many trees even with their branches to know the ropes.
Pick your poison -- previously everyone complained about the number
of branches in the tree.
FWIW, I've had far fewer complaints about tree management since
switching to the new practices. Of course, most of that is probably
attributable to pleasing dwmw2 (more-or-less)...
John
--
John W. Linville
linville@tuxdriver.com
prev parent reply other threads:[~2008-04-09 0:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 19:53 [PATCH 1/2] mac80211: fix recursive locking in ieee80211_sta_expire Jiri Slaby
2008-04-07 19:53 ` [PATCH 2/2] mac80211: fix defined but not used Jiri Slaby
2008-04-07 21:48 ` [PATCH 1/2] mac80211: fix recursive locking in ieee80211_sta_expire drago01
2008-04-08 14:29 ` Johannes Berg
2008-04-08 22:02 ` Jiri Slaby
2008-04-08 18:35 ` John W. Linville
2008-04-08 22:06 ` Jiri Slaby
2008-04-08 23:43 ` John W. Linville [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=20080408234321.GB23670@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=jirislaby@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.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).