linux-kernel - Re: linux-next: manual merge of the irqchip 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: <20211101153448.4ee33b3a@canb.auug.org.au>
Date:   Mon, 1 Nov 2021 15:34:48 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Palmer Dabbelt <palmer@...belt.com>,
        Paul Walmsley <paul@...an.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>
Cc:     Marc Zyngier <maz@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Mark Rutland <mark.rutland@....com>,
        Palmer Dabbelt <palmerdabbelt@...gle.com>,
        Tong Tiangen <tongtiangen@...wei.com>
Subject: Re: linux-next: manual merge of the irqchip tree with the risc-v
 tree

Hi all,

On Wed, 27 Oct 2021 13:55:50 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Today's linux-next merge of the irqchip tree got a conflict in:
> 
>   arch/riscv/Kconfig
> 
> between commit:
> 
>   dffe11e280a4 ("riscv/vdso: Add support for time namespaces")
> 
> from the risc-v tree and commit:
> 
>   0953fb263714 ("irq: remove handle_domain_{irq,nmi}()")
> 
> from the irqchip 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.
> 
> 
> diff --cc arch/riscv/Kconfig
> index 0050a2adf67b,353e28f5f849..000000000000
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@@ -62,8 -62,6 +62,7 @@@ config RISC
>   	select GENERIC_SCHED_CLOCK
>   	select GENERIC_SMP_IDLE_THREAD
>   	select GENERIC_TIME_VSYSCALL if MMU && 64BIT
>  +	select GENERIC_VDSO_TIME_NS if HAVE_GENERIC_VDSO
> - 	select HANDLE_DOMAIN_IRQ
>   	select HAVE_ARCH_AUDITSYSCALL
>   	select HAVE_ARCH_JUMP_LABEL if !XIP_KERNEL
>   	select HAVE_ARCH_JUMP_LABEL_RELATIVE if !XIP_KERNEL

This is now a conflict between the tip tree and the risc-v tree.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped