All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: John Linville <linville@tuxdriver.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: iwlwifi-next 2013-05-27
Date: Wed, 29 May 2013 09:01:20 +0200	[thread overview]
Message-ID: <1369810880.8414.0.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1369658029.14740.7.camel@jlt4.sipsolutions.net> (sfid-20130527_143407_283994_588E3186)

On Mon, 2013-05-27 at 14:33 +0200, Johannes Berg wrote:
> John,
> 
> I have accumulated a bunch of new things in iwlwifi-next. Unfortunately,
> to resolve a (semantic) conflict, I had to merge iwlwifi, which pulled
> in some ath9k/mwifiex changes we well since you didn't merge wireless
> into wireless-next at any point. If you want to handle this differently
> let me know. The shortlog below also looks inflated because of that,
> I've also pasted the 'real' one below the pull request.
> 
> The 'big features' I have are powersave related, including beacon
> filtering and connection monitor (which I have been sitting on for a
> while because it required a mac80211 patch) and thermal throttling/CT
> kill. The rest is mostly cleanups and small(ish) improvements.

Hm, withdrawn, we found a bunch of issues in the CT kill code. I'll
combine in a few fixes and then resend.

johannes


  reply	other threads:[~2013-05-29  7:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-27 12:33 pull-request: iwlwifi-next 2013-05-27 Johannes Berg
2013-05-29  7:01 ` Johannes Berg [this message]
2013-05-29  7:05 ` pull-request: iwlwifi-next 2013-05-29 Johannes Berg
2013-05-29 18:51   ` 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=1369810880.8414.0.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.