Determining patch impact on a specific config

[Greg KH]

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