linux-kernel - Re: linux-next: manual merge of the tip tree with the risc-v tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJF2gTQDjTAOjFBCL4oJCx0NnuBc_16M=1HEs54q+ehGX-mW3w@mail.gmail.com>
Date:   Thu, 26 May 2022 14:35:04 +0800
From:   Guo Ren <guoren@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Palmer Dabbelt <palmer@...belt.com>,
        Paul Walmsley <paul@...an.com>,
        Guo Ren <guoren@...ux.alibaba.com>,
        Ingo Molnar <mingo@...nel.org>,
        Juerg Haefliger <juerg.haefliger@...onical.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Palmer Dabbelt <palmer@...osinc.com>
Subject: Re: linux-next: manual merge of the tip tree with the risc-v tree

Safe manual merge, thx.

On Thu, May 26, 2022 at 11:02 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> Today's linux-next merge of the tip tree got a conflict in:
>
>   arch/x86/Kconfig
>
> between commit:
>
>   0cbed0ee1dbc ("arch: Add SYSVIPC_COMPAT for all architectures")
>
> from the risc-v tree and commit:
>
>   758cd94a0e16 ("x86/Kconfig: Fix indentation and add endif comments to arch/x86/Kconfig")
>
> from the tip tree.
>
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging.  You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc arch/x86/Kconfig
> index 98eaa8870f28,4d610ae216ce..000000000000
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@@ -2869,7 -2861,11 +2867,7 @@@ config COMPA
>   if COMPAT
>   config COMPAT_FOR_U64_ALIGNMENT
>         def_bool y
> - endif
>  -
>  -config SYSVIPC_COMPAT
>  -      def_bool y
>  -      depends on SYSVIPC
> + endif # COMPAT
>
>   endmenu
>


-- 
Best Regards
 Guo Ren

ML: https://lore.kernel.org/linux-csky/