On Thu, 6 Jun 2019 at 15:22, Sasha Levin <[email protected]> wrote:
>
> On Thu, Jun 06, 2019 at 12:25:13PM +0200, Ard Biesheuvel wrote:
> >Commit 60f38de7a8d4e816100ceafd1b382df52527bd50 upstream.
> >
> >Merge the parsing of the command line carried out in arm-stub.c with
> >the handling in efi_parse_options(). Note that this also fixes the
> >missing handling of CONFIG_CMDLINE_FORCE=y, in which case the builtin
> >command line should supersede the one passed by the firmware.
> >
> >Signed-off-by: Ard Biesheuvel <[email protected]>
> >Cc: Linus Torvalds <[email protected]>
> >Cc: Matt Fleming <[email protected]>
> >Cc: Peter Zijlstra <[email protected]>
> >Cc: Thomas Gleixner <[email protected]>
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Cc: [email protected]
> >Link: 
> >http://lkml.kernel.org/r/[email protected]
> >Signed-off-by: Ingo Molnar <[email protected]>
> >[ardb: fix up merge conflicts with 4.9.180]
> >Signed-off-by: Ard Biesheuvel <[email protected]>
> >---
> >This fixes the GCC build issue reported by Eike.
> >
> >Note that testing of arm64 stable kernels should cover CONFIG_RANDOMIZE_BASE,
> >since it has a profound impact on how the kernel binary gets put together.
>
> Should this fix be applied to 4.9 as well?
>
> I see it in 4.14+
>

I don't understand this question. The fix is proposed for v4.9 because
it fixes a build error with GCC that was caused by a backport of one
of the clang enablement patches.

Reply via email to