On 20/07/17 14:33, Daniel Kiper wrote: > On Thu, Jul 20, 2017 at 11:16:39AM +0200, Greg Kroah-Hartman wrote: >> On Thu, Jul 20, 2017 at 10:39:10AM +0200, Ingo Molnar wrote: >>> >>> * Daniel Kiper <daniel.kiper@xxxxxxxxxx> wrote: >>> >>>> Hey Greg, >>>> >>>> On Wed, Jul 19, 2017 at 11:43:32AM +0200, Greg Kroah-Hartman wrote: >>>>> 4.12-stable review patch. If anyone has any objections, please let me know. >>>> >>>> Why did you skip this patch for 4.11? IMO it should be applied there too. >>> >>> The thing is, this patch should probaly not even be in v4.12, as it should only >>> make any difference if there's a separate _bug_ in the kernel. >>> >>> This patch makes things more robust going forward, but I question that it needs to >>> be in -stable. >> >> Yeah, good point, I'm going to go drop it entirely from the 4.12-stable >> tree as it obviously isn't stable material, sorry for not catching that >> before. > > Wait a minute. IIRC, Juergen told me last week that this patch fixes a bug > found/assigned by/to him. Juergen? If it is true then I would apply it to > stable. If I am wrong you can drop it. I'm not sure both patches (this one and upstream 457ea3f7e97881f) are needed. I have got a report about a failing boot and with both patches applied the boot is working. I will ask if 457ea3f7e97881f alone works, too. If it doesn't I'll request this patch to be added to stable again. Juergen -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
