From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753566AbcKNHKd (ORCPT ); Mon, 14 Nov 2016 02:10:33 -0500 Received: from mail.linuxfoundation.org ([140.211.169.12]:36532 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751736AbcKNHKa (ORCPT ); Mon, 14 Nov 2016 02:10:30 -0500 Date: Mon, 14 Nov 2016 08:10:41 +0100 From: Greg KH To: "Levin, Alexander" Cc: "linux-kernel@vger.kernel.org" , Andrew Morton , "torvalds@linux-foundation.org" , "stable@vger.kernel.org" , "lwn@lwn.net" , Jiri Slaby Subject: Re: Linux 4.8.6 Message-ID: <20161114071041.GA32568@kroah.com> References: <20161031124710.GA31799@kroah.com> <20161031202639.GA14817@sasha-lappy> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161031202639.GA14817@sasha-lappy> User-Agent: Mutt/1.7.1 (2016-10-04) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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