On Thu, Jul 30, 2015 at 05:45:44PM +0100, Matt Fleming wrote:
> On Thu, 30 Jul, at 09:31:02AM, Greg KH wrote:
> >
> > Why isn't this an issue in newer kernel releases? Did this already get
> > fixed by some other patch? If so, why can't we just take that patch?
> > If not, why not?
>
> The commit 35d5134b7d5a ("x86/efi: Correct EFI boot stub use of
> code32_start") only exists in the stable trees in that form because
> there was quite a lot of churn in that area in Linus tree that didn't
> get backported.
>
> So the code in Linus' tree never looked like the code in the stable does
> right now.
>
> > I _REALLY_ don't like taking patches that are not already in Linus's
> > tree, as it almost always turns out to be the wrong solution.
>
> Yeah, I think this issue verifies that.
Ugh, what a mess. Ok, if you get something that works and is in a
format that I can apply it, please resend it properly so that we can do
so.
thanks,
greg k-h
--
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
