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] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 18 Feb 2021 15:48:57 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
        ARM <linux-arm-kernel@...ts.infradead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>
Cc:     Marc Zyngier <maz@...nel.org>, Maxime Ripard <mripard@...nel.org>,
        Chen-Yu Tsai <wens@...e.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Maxime Ripard <maxime@...no.tech>,
        Paul Kocialkowski <contact@...lk.fr>,
        Samuel Holland <samuel@...lland.org>
Subject: Re: linux-next: manual merge of the irqchip tree with the sunxi
 tree

Hi all,

On Mon, 15 Feb 2021 09:11:24 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Mon, 1 Feb 2021 14:42:59 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> >
> > Today's linux-next merge of the irqchip tree got a conflict in:
> > 
> >   Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml
> > 
> > between commit:
> > 
> >   752b0aac99c7 ("dt-bindings: irq: sun7i-nmi: Add binding documentation for the V3s NMI")
> > 
> > from the sunxi tree and commit:
> > 
> >   ad6b47cdef76 ("dt-bindings: irq: sun6i-r: Split the binding from sun7i-nmi")
> > 
> > from the irqchip tree.
> > 
> > I fixed it up (I think - 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 Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml
> > index 4fd1e2780026,f34ecc8c7093..000000000000
> > --- a/Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml
> > +++ b/Documentation/devicetree/bindings/interrupt-controller/allwinner,sun7i-a20-sc-nmi.yaml
> > @@@ -25,17 -25,7 +25,10 @@@ properties
> >         - const: allwinner,sun6i-a31-sc-nmi
> >           deprecated: true
> >         - const: allwinner,sun7i-a20-sc-nmi
> > -       - items:
> > -           - const: allwinner,sun8i-a83t-r-intc
> > -           - const: allwinner,sun6i-a31-r-intc
> >  +      - items:
> >  +          - const: allwinner,sun8i-v3s-nmi
> >  +          - const: allwinner,sun9i-a80-nmi
> >         - const: allwinner,sun9i-a80-nmi
> > -       - items:
> > -           - const: allwinner,sun50i-a64-r-intc
> > -           - const: allwinner,sun6i-a31-r-intc
> >         - items:
> >             - const: allwinner,sun50i-a100-nmi
> >             - const: allwinner,sun9i-a80-nmi  
> 
> With the merge window about to open, this is a reminder that this
> conflict still exists.  It is now between the arm-soc tree and the
> irqchip tree.

This is now a conflict between the arm-soc tree and the tip tree.

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ