mirror of https://lore.kernel.org/lkml/
 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: pull request: wireless-next 2011-08-02
Date: Tue, 02 Aug 2011 17:06:37 -0700 (PDT)	[thread overview]
Message-ID: <20110802.170637.389945963010848876.davem@davemloft.net> (raw)
In-Reply-To: <20110802.143955.1785360722763378138.davem@davemloft.net>

From: David Miller <davem@davemloft.net>
Date: Tue, 02 Aug 2011 14:39:55 -0700 (PDT)

> From: "John W. Linville" <linville@tuxdriver.com>
> Date: Tue, 2 Aug 2011 14:11:31 -0400
> 
>> Here are a few more fixes intended for 3.1.  Dan Carpenter gives us an
>> off-by-one fix in the scan trigger code for nl80211.  Felix gives us a
>> fix for tx power initialization for ath9k.  Larry fixes an oops on ARM
>> by rewriting some init code to avoid checking something that doesn't get
>> initialized on ARM.  This round's big hero is Stanislaw, who gives us a
>> brown paper bag fix for some skb handling in rt2x00, an ath9k fix to
>> avoid hangs on systems w/ ASPM disabled, and an iwlegacy fix to ensure
>> that tx power settings are applied properly.
>> 
>> Please let me know if there are problems!
> 
> I'll pull this, but I think once you've sent me all of your features
> for the merge window you should drop "-next" from the name of the
> tree and/or branches you ask me to pull from.
> 
> This makes it entirely clear that you're sending me bug fixes and not
> features and cleanups.

Well, this thing is not based upon the plain net GIT tree, because
when I pull it I get a bunch of things from Linus's tree which are
not in the net tree yet.

Please fix this up.

Thanks.

      reply	other threads:[~2011-08-03  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-02 18:11 John W. Linville
2011-08-02 21:39 ` David Miller
2011-08-03  0:06   ` 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=20110802.170637.389945963010848876.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®