All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "Nico Schottelius" <nico-linux-20111017@schottelius.org>,
	"Eric Dumazet" <eric.dumazet@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: BUG: All network processes hang (brcmsmac/wpa_supplicant)
Date: Sat, 22 Oct 2011 10:44:46 +0200	[thread overview]
Message-ID: <4EA2827E.1030502@broadcom.com> (raw)
In-Reply-To: <20111022083005.GA6032@suse.de>

On 10/22/2011 10:30 AM, Greg KH wrote:
> On Sat, Oct 22, 2011 at 01:13:34AM -0700, Arend Van Spriel wrote:
>>> From: Nico Schottelius [mailto:nico-linux-20111017@schottelius.org]
>>> Sent: zaterdag 22 oktober 2011 4:00
>>>
>>> Hey Arend,
>>>
>>> it seems that your patch really solves this problem.
>>
>> Great. This fix is in linux-next tree.
>>
>> Greg,
>>
>> This problem causes packets to get dropped on 5GHz. Should I
>> sent a patch for 3.1 (staging-linus) for this? It is already
>> fixed in wireless-next.
> 
> No, just wait for it to get into Linus's tree for 3.2-rc1, and then
> email the git commit id to stable@vger.kernel.org so it will be added to
> the 3.1-stable releases.
> 
> greg k-h
> 

Thanks, Greg

Saw you email regarding staging-next so I was not sure about
staging-linus. Will be patient ;-)

Gr. AvS


  reply	other threads:[~2011-10-22  8:45 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-18 11:14 BUG: All network processes hang (brcmsmac/wpa_supplicant) Nico Schottelius
2011-10-18 12:24 ` Eric Dumazet
2011-10-19 12:36   ` Nico Schottelius
2011-10-19 12:36     ` Nico Schottelius
2011-10-19 12:49     ` Eric Dumazet
2011-10-19 12:58       ` Arend van Spriel
2011-10-19 13:05         ` Eric Dumazet
2011-10-19 13:05           ` Eric Dumazet
2011-10-19 13:09           ` Nico Schottelius
2011-10-19 13:07       ` Nico Schottelius
2011-10-19 14:28         ` Nico Schottelius
2011-10-19 14:28         ` Nico Schottelius
2011-10-19 14:43           ` Arend van Spriel
2011-10-19 14:55             ` Nico Schottelius
2011-10-19 16:48               ` Arend van Spriel
2011-10-19 16:48               ` Arend van Spriel
2011-10-19 21:42                 ` Nico Schottelius
2011-10-20  6:28                   ` Arend van Spriel
2011-10-22  1:59                     ` Nico Schottelius
2011-10-22  8:13                       ` Arend Van Spriel
2011-10-22  8:30                         ` Greg KH
2011-10-22  8:44                           ` Arend van Spriel [this message]
2011-10-23 10:04                       ` Arend van Spriel
2011-10-23 10:53                         ` Nico Schottelius
2011-10-23 19:48                           ` Nico Schottelius
2011-10-24 12:50                             ` Arend van Spriel
2011-10-25  6:41                               ` Nico Schottelius
2011-10-20  6:28                   ` Arend van Spriel
2011-10-19 14:43           ` Arend van Spriel
2011-10-19 14:46           ` Eric Dumazet
2011-10-19 14:58             ` Nico Schottelius
2011-10-18 13:14 ` Arend van Spriel
2011-10-18 13:34   ` Nico Schottelius

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=4EA2827E.1030502@broadcom.com \
    --to=arend@broadcom.com \
    --cc=eric.dumazet@gmail.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nico-linux-20111017@schottelius.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 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.