From: Jiri Slaby <jirislaby@gmail.com>
To: "John W. Linville" <linville@tuxdriver.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: Wed, 09 Apr 2008 00:06:03 +0200 [thread overview]
Message-ID: <47FBEC4B.7030205@gmail.com> (raw)
In-Reply-To: <20080408183556.GC8183@tuxdriver.com>
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.
> Please use the wireless-testing tree for development, as it contains
> both sets of patches (fixes for the current release and updates for the
> future) as well as a few extras (like drivers still in development).
> Plus it is somewhat more stable, being based off the most a recent
> -rc release rather than just whatever someone last pulled.
Ok, thanks.
next prev parent reply other threads:[~2008-04-08 22:06 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 [this message]
2008-04-08 23:43 ` 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=47FBEC4B.7030205@gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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.