All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Greg KH" <gregkh@suse.de>
Cc: "Sukesh Srikakula" <sukeshs@broadcom.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/2] brcm80211: Fix for suspend/resume bug
Date: Tue, 3 May 2011 14:33:44 +0200	[thread overview]
Message-ID: <4DBFF628.6040502@broadcom.com> (raw)
In-Reply-To: <20110503121522.GB22674@suse.de>

On 05/03/2011 02:15 PM, Greg KH wrote:
> On Tue, May 03, 2011 at 12:00:57AM -0700, sukeshs@broadcom.com wrote:
>>   #if defined(CONFIG_PM_SLEEP)
>>
>> +extern volatile bool dhd_mmc_suspend;
> This does not do what you think it does.

Hi Greg,

I posted the 'catchup' patch set and I rebased it on '[PATCH 1/2] 
brcm80211: FIX for TKIP GTK bug' from Sukesh. The only other two patches 
I saw on the linuxdriver list are:

staging: brcm80211: brcmfmac: Add and use dhd_dbg [joe@perches.com] => 
he rejected it himself.
STAGING: brcm80211 SDIO/MMC cleanups [grundler@chromium.org] => does not 
apply.

So I discarded those two as well.

Gr. AvS


  reply	other threads:[~2011-05-03 12:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03  7:00 [PATCH 0/2] *** SUBJECT HERE *** sukeshs
2011-05-03  7:00 ` [PATCH 1/2] brcm80211: FIX for TKIP GTK bug sukeshs
2011-05-03  7:00 ` [PATCH 2/2] brcm80211: Fix for suspend/resume bug sukeshs
2011-05-03  9:10   ` Arend van Spriel
2011-05-03 12:15   ` Greg KH
2011-05-03 12:33     ` Arend van Spriel [this message]
2011-05-03 13:00       ` Greg KH
2011-05-03 13:09         ` Arend van Spriel
2011-05-03 13:11           ` Greg KH
2011-05-03 13:17             ` Arend van Spriel
2011-05-03 13:41               ` Arend van Spriel
2011-05-03 19:46                 ` Greg KH
2011-05-03 12:14 ` [PATCH 0/2] *** SUBJECT HERE *** 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=4DBFF628.6040502@broadcom.com \
    --to=arend@broadcom.com \
    --cc=devel@linuxdriverproject.org \
    --cc=gregkh@suse.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sukeshs@broadcom.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.