stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: arend.vanspriel@broadcom.com, cernekee@chromium.org,
	franky.lin@broadcom.com, hante.meuleman@broadcom.com,
	kvalo@codeaurora.org, pieter-paul.giesberts@broadcom.com
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "brcmfmac: add length check in brcmf_cfg80211_escan_handler()" has been added to the 4.4-stable tree
Date: Tue, 10 Oct 2017 21:31:30 +0200	[thread overview]
Message-ID: <20171010193130.GA20122@kroah.com> (raw)
In-Reply-To: <150765937788189@kroah.com>

On Tue, Oct 10, 2017 at 08:16:17PM +0200, gregkh@linuxfoundation.org wrote:
> 
> This is a note to let you know that I've just added the patch titled
> 
>     brcmfmac: add length check in brcmf_cfg80211_escan_handler()
> 
> to the 4.4-stable tree which can be found at:
>     http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>      brcmfmac-add-length-check-in-brcmf_cfg80211_escan_handler.patch
> and it can be found in the queue-4.4 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
> 

Nope, breaks the build.  If this should go to 4.4, can someone please
provide a working backport for it?

thanks,

greg k-h

  reply	other threads:[~2017-10-10 19:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 18:16 Patch "brcmfmac: add length check in brcmf_cfg80211_escan_handler()" has been added to the 4.4-stable tree gregkh
2017-10-10 19:31 ` Greg KH [this message]
2017-10-12  9:14   ` Arend van Spriel
  -- strict thread matches above, loose matches on Subject: below --
2017-10-12 11:58 gregkh

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=20171010193130.GA20122@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arend.vanspriel@broadcom.com \
    --cc=cernekee@chromium.org \
    --cc=franky.lin@broadcom.com \
    --cc=hante.meuleman@broadcom.com \
    --cc=kvalo@codeaurora.org \
    --cc=pieter-paul.giesberts@broadcom.com \
    --cc=stable-commits@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).