From: Greg KH <gregkh@linuxfoundation.org>
To: mcgrof@kernel.org
Cc: stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "firmware: fix NULL pointer dereference in __fw_load_abort()" has been added to the 4.9-stable tree
Date: Sun, 5 Feb 2017 11:44:28 +0100 [thread overview]
Message-ID: <20170205104428.GA3510@kroah.com> (raw)
In-Reply-To: <14862904140157@kroah.com>
On Sun, Feb 05, 2017 at 11:26:54AM +0100, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> firmware: fix NULL pointer dereference in __fw_load_abort()
>
> to the 4.9-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:
> firmware-fix-null-pointer-dereference-in-__fw_load_abort.patch
> and it can be found in the queue-4.9 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.
Ugh, no, this breaks the build horribly. And in looking at the patch
itself, your marking this for stable doesn't make sense. Why did you do
that? This seems to be only an issue for 4.10-rc at the moment.
Now dropped from the stable trees, for this, and for 4.4.
thanks,
greg k-h
next prev parent reply other threads:[~2017-02-05 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-05 10:26 Patch "firmware: fix NULL pointer dereference in __fw_load_abort()" has been added to the 4.9-stable tree gregkh
2017-02-05 10:44 ` Greg KH [this message]
[not found] ` <CAB=NE6X9GbH=qa+CBMOBU6hG3J4zc7jHh9nsVTQ70CM_j3c=EA@mail.gmail.com>
[not found] ` <CAB=NE6Vg9pMpUhzPveXDozxKquArpBs5dXBjcteHsXAN-Hv1Qg@mail.gmail.com>
[not found] ` <CAB=NE6X8Rz5PeMLy4=Oe=scCPJyr2YWJD-Z4AC1cwgZWWN2CYw@mail.gmail.com>
[not found] ` <CAB=NE6VGLXxBxde0nWERBX=Sbko-P4j07ogqV2=FsM_CV3k6ig@mail.gmail.com>
2017-02-06 8:45 ` Greg Kroah-Hartman
2017-02-06 17:27 ` Luis R. Rodriguez
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=20170205104428.GA3510@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mcgrof@kernel.org \
--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).