linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: eddie@ehuk.net, stable@vger.kernel.org, florian@reitmeir.org,
	linux-wireless@vger.kernel.org, j@w1.fi
Subject: Re: Linux 3.6.5
Date: Wed, 7 Nov 2012 08:36:34 +0100	[thread overview]
Message-ID: <20121107073634.GA6560@kroah.com> (raw)
In-Reply-To: <1352233894.8814.10.camel@jlt4.sipsolutions.net>

On Tue, Nov 06, 2012 at 09:31:34PM +0100, Johannes Berg wrote:
> On Tue, 2012-11-06 at 19:35 +0000, Eddie Chapman wrote:
> 
> > > Right, we're still looking at that. It seems that it's not an ideal
> > > solution, the regulatory change I proposed is probably better. Could you
> > > check if it helps as well? That is, remove this patch, and apply this
> > > one: http://p.sipsolutions.net/8877cbe3440d94b1.txt
> > 
> > OK, so I've removed 0129f39c7d882289.txt, applied 8877cbe3440d94b1.txt, 
> > and I've kept 3a40414f826a8f1096d9b94c4a53ef91b25ba28d applied.
> > 
> > Rebooted, and happy to report throughput is still good, so 
> > 8877cbe3440d94b1.txt also "fixes" it for me.
> 
> Great, thanks. I'm not really sure which one to apply, and if we apply
> the 8877 one we'll also want to update the reg db (that you aren't
> using). A lot of people are in Barcelona right now though, so that might
> be a week or so until we can close this.

I'm in Barcelona all this week, but a nice summary of what I'm supposed
to do here for the stable tree would be great to have when ever you
figure it out, don't wait for me to return, my email queues up just fine :)

thanks,

greg k-h

  parent reply	other threads:[~2012-11-07  7:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20121031173811.GA12970@kroah.com>
     [not found] ` <509575F4.5020109@ehuk.net>
     [not found]   ` <20121105081757.GA3730@kroah.com>
2012-11-05 11:04     ` Linux 3.6.5 Eddie Chapman
2012-11-05 12:01       ` Johannes Berg
2012-11-05 22:08         ` Eddie Chapman
2012-11-06  7:57           ` Johannes Berg
2012-11-06 15:34             ` Eddie Chapman
2012-11-06 15:54               ` Johannes Berg
2012-11-06 16:23                 ` Eddie Chapman
2012-11-06 16:39                 ` Johannes Berg
2012-11-06 16:47                   ` Johannes Berg
2012-11-06 16:50                   ` Eddie Chapman
2012-11-06 16:55                     ` Johannes Berg
2012-11-06 16:57                       ` Johannes Berg
2012-11-06 17:07                         ` Eddie Chapman
2012-11-06 17:16                           ` Johannes Berg
2012-11-06 18:59                 ` Eddie Chapman
2012-11-06 19:20                   ` Johannes Berg
2012-11-06 19:35                     ` Eddie Chapman
2012-11-06 20:31                       ` Johannes Berg
2012-11-06 20:38                         ` Eddie Chapman
2012-11-07  7:36                         ` Greg KH [this message]
2012-11-07  7:53                           ` Johannes Berg
2012-11-07  8:09                             ` Greg KH

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=20121107073634.GA6560@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=eddie@ehuk.net \
    --cc=florian@reitmeir.org \
    --cc=j@w1.fi \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stable@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).