From: "John W. Linville" <linville@tuxdriver.com>
To: linux-wireless@vger.kernel.org
Subject: caught-up on merging for 2.6.38 -next wireless bits
Date: Tue, 16 Nov 2010 17:08:05 -0500 [thread overview]
Message-ID: <20101116220804.GA21198@tuxdriver.com> (raw)
All,
I have finally (more-or-less) cleared my patch queue for 2.6.38 -next
bits. If you are waiting to see patches posted prior to last week
show-up in wireless-testing then you may want to ping me about them.
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next reply other threads:[~2010-11-16 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 22:08 John W. Linville [this message]
2010-11-18 8:02 ` caught-up on merging for 2.6.38 -next wireless bits Rafał Miłecki
2010-11-22 20:35 ` 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=20101116220804.GA21198@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 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.