From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: wireless-next-2.6 2008-06-03
Date: Mon, 9 Jun 2008 16:42:41 -0400 [thread overview]
Message-ID: <20080609204241.GA11343@tuxdriver.com> (raw)
In-Reply-To: <20080603194927.GA9590-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
On Tue, Jun 03, 2008 at 03:49:27PM -0400, John W. Linville wrote:
> Tons of new stuff intended for 2.6.27. Please let me know if there are
> problems!
> Dan Williams (1):
> ipw2200: queue direct scans
I'm sending this one with the next round of fixes. I'll reformulate
this request and resend.
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-09 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 12:40 pull request: wireless-next-2.6 2008-05-22 John W. Linville
[not found] ` <20080522124017.GA3996-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-03 18:53 ` John W. Linville
[not found] ` <20080603185301.GA28966-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-03 19:49 ` pull request: wireless-next-2.6 2008-06-03 John W. Linville
[not found] ` <20080603194927.GA9590-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-09 20:42 ` John W. Linville [this message]
[not found] ` <20080609204241.GA11343-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-06-09 21:07 ` pull request: wireless-next-2.6 2008-06-09 John W. Linville
2008-06-10 9:19 ` David Miller
2008-06-10 12:17 ` 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=20080609204241.GA11343@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).