From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: Re: wireless-next-2.6 rebased 2010-11-24
Date: Wed, 24 Nov 2010 16:14:29 -0500 [thread overview]
Message-ID: <20101124211428.GA9351@tuxdriver.com> (raw)
In-Reply-To: <20101124170956.GE7435@tuxdriver.com>
On Wed, Nov 24, 2010 at 12:09:56PM -0500, John W. Linville wrote:
> Rebased to drop a problematic patch -- FYI!
I messed this up -- don't rebase any downstream trees yet...
--
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-11-24 21:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 17:09 wireless-next-2.6 rebased 2010-11-24 John W. Linville
2010-11-24 21:14 ` John W. Linville [this message]
2010-11-24 21:55 ` 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=20101124211428.GA9351@tuxdriver.com \
--to=linville@tuxdriver.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).