linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arend van Spriel <arend@broadcom.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: <stable@vger.kernel.org>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH for-3.12] brcmfmac: handle IF event for P2P_DEVICE interface
Date: Tue, 23 Sep 2014 15:55:40 +0200	[thread overview]
Message-ID: <54217BDC.5060308@broadcom.com> (raw)
In-Reply-To: <20140923135129.GA12636@kroah.com>

On 09/23/14 15:51, Greg KH wrote:
> On Tue, Sep 23, 2014 at 03:42:42PM +0200, Arend van Spriel wrote:
>> On 09/23/14 15:22, Greg KH wrote:
>>> On Tue, Sep 23, 2014 at 11:52:26AM +0200, Arend van Spriel wrote:
>>>> upstream: 87c4790330810fe5caf0172d9320cf24ef19cebe
>>>
>>> That commit id doesn't match anything in Linus's tree :(
>>>
>>
>> Hmmm, that is weird:
>>
>> [arend@lb-bun-235 ~/scm/brcm80211-next]
>> $ git remote show torvalds
>> * remote torvalds
>>    Fetch URL:
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>    Push  URL:
>> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>>    HEAD branch: master
>>    Remote branch:
>>      master tracked
>> [arend@lb-bun-235 ~/scm/brcm80211-next]
>> $ git log torvalds/master --oneline -8 -- drivers/net/wireless/brcm80211
>> *87c4790 brcmfmac: handle IF event for P2P_DEVICE interface*
>> 8f2b459 brcmfmac: obtain ifp through wdev structure
>> f1d5603 brcmfmac: conditionally compile firmware protocol source code
>> fac7d2a brcmfmac: Fix memory leak and missing assignment.
>> 2d116b88 brcmfmac: fix memory leakage in msgbuf
>> ebcc2f5 brcmfmac: fix curly brace mistake in brcmf_pcie_handle_mb_data()
>> aef4f5b Merge tag 'master-2014-07-31' of
>> git://git.kernel.org/pub/scm/linux/kern
>> 70b7d94 brcmfmac: Add TDLS support to msgbuf.
>
> Ah, it just went in, sorry for the noise.
>
> But it _just_ went in, why are you emailing this?  We have to wait for a
> -rc release to come out with the patch before being able to add it to
> the tree.

Noted. Did not find that nitty gritty detail in stable_kernel_rules.txt, 
but I just might create a patch for that if I can beat my writers block ;-)

Gr. AvS

> thanks,
>
> greg k-h


      reply	other threads:[~2014-09-23 13:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23  9:52 [PATCH for-3.12] brcmfmac: handle IF event for P2P_DEVICE interface Arend van Spriel
2014-09-23 13:22 ` Greg KH
2014-09-23 13:42   ` Arend van Spriel
2014-09-23 13:51     ` Greg KH
2014-09-23 13:55       ` Arend van Spriel [this message]

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=54217BDC.5060308@broadcom.com \
    --to=arend@broadcom.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --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).