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-next-2.6 2009-09-23
Date: Wed, 23 Sep 2009 16:24:49 -0700 (PDT) [thread overview]
Message-ID: <20090923.162449.141768862.davem@davemloft.net> (raw)
In-Reply-To: <20090923155339.GA14597@tuxdriver.com>
From: "John W. Linville" <linville@tuxdriver.com>
Date: Wed, 23 Sep 2009 11:53:40 -0400
> Please accept this one last round of wireless bits for the merge window.
> They are fixes for the most part, and the teams involved are very eager
> to have these for the 2.6.32 cycle. In particular, the b43 and ath9k
> teams have some late breakers -- yes, I have reminded them of the
> process, but they are quite insistent...
>
> Please let me know if there are problems!
Pulled, but yes you guys need to stick to pure bug fixes at
this point, please.
Also, please put the branch name, even if it's simply 'master'
in your GIT pull urls you give me.
Thanks.
next prev parent reply other threads:[~2009-09-23 23:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 15:53 John W. Linville
2009-09-23 23:24 ` David Miller [this message]
2009-09-24 3:50 ` 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=20090923.162449.141768862.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
all inboxes | Powered by JetHome®