On Sat, Mar 12, 2016 at 01:55:44PM +0800, Ard Biesheuvel wrote: > > > > On 12 mrt. 2016, at 13:50, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > >> On Sat, Mar 12, 2016 at 08:51:26AM +0700, Ard Biesheuvel wrote: > >>> On 8 March 2016 at 20:45, Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> wrote: > >>>> On 8 March 2016 at 20:44, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > >>>>> On Tue, Mar 08, 2016 at 05:40:14PM +0700, Ard Biesheuvel wrote: > >>>>>> On 8 March 2016 at 07:02, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > >>>>>> 4.4-stable review patch. If anyone has any objections, please let me know. > >>>>> > >>>>> Please hold off on this one. We are seeing some breakage on 64k pages systems > >>>> > >>>> If this problem is also in Linus's tree, I'd like to keep it in to keep > >>>> things "bug compatible". Please let me know what fix that I should > >>>> apply to resolve this. > >>> > >>> I am about to send out the patch that should fix this, so I will put you on cc. > >> > >> Not sure what happened here, but this patch is in 4.4-stable now, but > >> the fix is not. > > > > Because the fix came out _after_ I released that kernel? I can't go > > back in time... > > > > I kind of got the whole chronology thing. I am just surprised you > pulled only that patch (and not the fix) anyway, since you knew it > would break things, and that a fix was on the way. That way I knew you all would work quickly to get the fix in :) We do this all the time, nothing new here, being "bug compatible" is good... thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html