netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: pullreq: wireless-next-2.6 2010-03-03
Date: Wed, 03 Mar 2010 22:44:23 -0800 (PST)	[thread overview]
Message-ID: <20100303.224423.226765329.davem@davemloft.net> (raw)
In-Reply-To: <20100303212638.GI23920@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 3 Mar 2010 16:26:39 -0500

> Here is another quick batch intended for 2.6.34.  Included are a
> USB ID, some small fixes, and a few (for async firmware loading and
> KEY_RFKILL) that depended on patches that weren't in the net-next-2.6
> tree until after the merge window opened.
> 
> Please let me know if there are problems!

Pulled, thanks John.

      reply	other threads:[~2010-03-04  6:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03 21:26 pullreq: wireless-next-2.6 2010-03-03 John W. Linville
2010-03-04  6:44 ` David Miller [this message]

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=20100303.224423.226765329.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).