From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull request: wireless-2.6 'upstream' 2008-01-22
Date: Tue, 22 Jan 2008 19:04:56 -0800 (PST) [thread overview]
Message-ID: <20080122.190456.206906647.davem@davemloft.net> (raw)
In-Reply-To: <20080123014521.GG3206@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Tue, 22 Jan 2008 20:45:21 -0500
> git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-2.6.git upstream
Pulled and pushed out to net-2.6.25, thanks!
next prev parent reply other threads:[~2008-01-23 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 1:45 pull request: wireless-2.6 'upstream' 2008-01-22 John W. Linville
2008-01-23 3:04 ` David Miller [this message]
[not found] ` <20080123014521.GG3206-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2008-01-23 11:15 ` Stefano Brivio
2008-01-23 11:30 ` Michael Buesch
[not found] ` <200801231230.07734.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2008-01-23 12:46 ` John W. Linville
2008-01-23 12:41 ` 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=20080122.190456.206906647.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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).