On Thu, 18 Feb, at 09:15:28PM, Rafael J. Wysocki wrote: > > Actually, the reason is that, as a rule, the process for ACPICA > patches is that they first go to upstream ACPICA and they are acquired > by Linux from there. > > While there are some exceptions from that process, there also are good > reasons for that process to be followed, including the licensing one > mentioned by Lv. > > All that said, Matt, if you agree that the patch can be applied under > the BSD license, I think we can offer help with converting it to the > upstream ACPICA coding conventions and applying it there. Lv, would > you be able to take care of that? I don't have any problem with that, but can we hold off on this patch for now? There's another approach to fixing the BGRT issue with kexec that's being discussed which would supersede this, https://lkml.kernel.org/r/20160218141544.GH2651 at codeblueprint.co.uk Assuming this patch does get picked up again, I'm happy to respin it against upstream ACPICA, but how do I go about getting dependent patches merged, PATCH 2/2 in this case?