From: Greg KH <gregkh@linuxfoundation.org>
To: "Levin, Alexander" <alexander.levin@verizon.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"lwn@lwn.net" <lwn@lwn.net>, Jiri Slaby <jslaby@suse.cz>
Subject: Re: Linux 4.8.6
Date: Mon, 14 Nov 2016 08:10:41 +0100 [thread overview]
Message-ID: <20161114071041.GA32568@kroah.com> (raw)
In-Reply-To: <20161031202639.GA14817@sasha-lappy>
On Mon, Oct 31, 2016 at 04:26:39PM -0400, Levin, Alexander wrote:
> On Mon, Oct 31, 2016 at 06:47:10AM -0600, Greg KH wrote:
> > I'm announcing the release of the 4.8.6 kernel.
>
> Hey Greg,
>
> I've put more work into improving my filters to find stable commits upstream.
>
> The list below, taken from v4.8..v4.9-rc2 commits contains mostly commits that aren't tagged for stable, but should probably be there. In this case, it also includes one CVE fix that falls under that description.
>
> Note that I've filtered "prerequisite" commits out to leave only the actual commits we're interested in, so for example - for the first commit on the list you'd need either bbdc070 ("drm/i915: rename macro parameter(ring) to (engine)") or backport those changes yourself. If the list below looks good to you I can send you a pull request with a complete branch.
[what happened to wrapping email lines...]
This looks good, but it's a lot of patches, what are you using to
determine what "should be here"? I should have caught up with all of
the patches marked as "stable@", and almost all of the ones that looked
correct that were marked with "fixes:", so is there any way you can
rebase your tree to see what is left?
And yes, a git tree would be great to pull from, that makes it easier to
look at for me.
thanks,
greg k-h
prev parent reply other threads:[~2016-11-14 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 12:47 Greg KH
2016-10-31 12:47 ` Greg KH
2016-10-31 20:26 ` Levin, Alexander
2016-11-14 7:10 ` Greg KH [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=20161114071041.GA32568@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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
Powered by JetHome