From mboxrd@z Thu Jan  1 00:00:00 1970
From: greg@kroah.com (Greg KH)
Date: Thu, 18 Aug 2016 09:38:43 +0200
Subject: Determining patch impact on a specific config
In-Reply-To: <20160817184853.GA29334@osadl.at>
References: <20160817123939.GA27134@osadl.at> <20160817132544.GA320@kroah.com>
	<20160817135216.GA1401@kroah.com> <20160817140128.GA28158@osadl.at>
	<20160817141719.GA4270@kroah.com> <20160817144922.GA28282@osadl.at>
	<20160817153927.GC5876@kroah.com> <20160817165029.GA28831@osadl.at>
	<20160817173402.GA10074@kroah.com>
	<20160817184853.GA29334@osadl.at>
Message-ID: <20160818073843.GB6078@kroah.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

On Wed, Aug 17, 2016 at 06:48:53PM +0000, Nicholas Mc Guire wrote:
> > The first one makes this easier for you, the second and third are not
> > always true.  There have been big patchsets get merged into longterm
> > stable kernel releases that were done because they were "optimizations"
> > and the maintainer of that subsystem and I discussed it and deemed it
> > was a valid thing to accept.  This happens every 6 months or so if you
> > look closely.  The mm subsystem is known for this :)
> 
> so major mm subsystem optimizations will go in in the middle of a 
> LTS between "random" sublevel releases ? Atleast for 4.4-4.4.13 I was not
> able to pin-point such a change (based on files-changes/lines-added/removed)
> could you point me to the one or other ? would help to see why we missed it.

4.4 hasn't been around long enough for this to happen yet, I think it
happened in 4.1, or maybe 3.14, or possibly 3.10, can't remember, but it
should be obvious by the changelogs.

thanks,

greg "just one more email!" k-h