From: "John W. Linville" <linville@tuxdriver.com>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: wireless-testing rebased on 2.6.38-rc1
Date: Wed, 19 Jan 2011 17:23:52 -0500 [thread overview]
Message-ID: <20110119222352.GA16160@tuxdriver.com> (raw)
In-Reply-To: <4D376309.9020300@candelatech.com>
On Wed, Jan 19, 2011 at 02:17:45PM -0800, Ben Greear wrote:
> On 01/19/2011 10:22 AM, John W. Linville wrote:
> >The wireless-testing tree has been rebased upon 2.6.38-rc1.
> >Please updates your trees accordingly.
>
> Did you remove the 'wl' from the kernel name on purpose?
>
> (Or did I screw that up locally somehow?)
Arg...no...
I'll fix it...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-01-19 22:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 18:22 wireless-testing rebased on 2.6.38-rc1 John W. Linville
2011-01-19 22:17 ` Ben Greear
2011-01-19 22:23 ` 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=20110119222352.GA16160@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=greearb@candelatech.com \
--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).