From: Greg KH <greg@kroah.com>
To: Arend van Spriel <arend@broadcom.com>
Cc: Greg KH <gregkh@suse.de>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Sukesh Srikakula <sukeshs@broadcom.com>
Subject: Re: [PATCH 2/2] brcm80211: Fix for suspend/resume bug
Date: Tue, 3 May 2011 12:46:49 -0700 [thread overview]
Message-ID: <20110503194649.GA6322@kroah.com> (raw)
In-Reply-To: <4DC0061E.8020504@broadcom.com>
On Tue, May 03, 2011 at 03:41:50PM +0200, Arend van Spriel wrote:
> On 05/03/2011 03:17 PM, Arend van Spriel wrote:
> >On 05/03/2011 03:11 PM, Greg KH wrote:
> >>On Tue, May 03, 2011 at 03:09:20PM +0200, Arend van Spriel wrote:
> >>>On 05/03/2011 03:00 PM, Greg KH wrote:
> >>>>On Tue, May 03, 2011 at 02:33:44PM +0200, Arend van Spriel wrote:
> >>>>>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:
> >>>>You rebased on a 1/2 patch in a series with an invalid 0/2 email?
> >>>>
> >>>>{sigh}
> >>>Sorry.
> >>>>I dropped that patch as the whole series needed to be resent, do you
> >>>>want me to apply that one patch before yours?
> >>>I can resend my series if that is more convenient for you.
> >>Please, but just send it to me, I doubt everyone wants to see 60+
> >>patches again on the list.
> >Ok. Just for this time I will agree to break the rules ;-)
>
> Hi Greg,
>
> I rebase and regenerated the patch files. Did a diff before
> resending them with the previous set and there are no relevant
> differences so the patches I sent this morning are ok.
Great, I've applied them all now.
greg k-h
next prev parent reply other threads:[~2011-05-03 19:49 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
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 [this message]
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=20110503194649.GA6322@kroah.com \
--to=greg@kroah.com \
--cc=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 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).