From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2010-01-18
Date: Tue, 19 Jan 2010 02:04:37 -0800 (PST) [thread overview]
Message-ID: <20100119.020437.21924341.davem@davemloft.net> (raw)
In-Reply-To: <20100118222208.GA28686@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Mon, 18 Jan 2010 17:22:09 -0500
> Here are a few more fixes intended for 2.6.33 -- I don't think there
> is anything controversial this time. :-) The biggest one just adds
> some copyright notices to a couple of files. Everything else is
> more-or-less one-liner stuff, and one adds a device ID...
>
> Please let me know if there are problems!
Pulled, thanks John.
next prev parent reply other threads:[~2010-01-19 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 22:22 pull request: wireless-2.6 2010-01-18 John W. Linville
2010-01-19 10:04 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-18 20:21 John W. Linville
2011-01-18 20:51 ` David Miller
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=20100119.020437.21924341.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).