linux-kernel - linux-next: manual merge of the nds32 tree with the asm-generic 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>] [day] [month] [year] [list]

Message-ID: <20180315105103.421ba79c@canb.auug.org.au>
Date:   Thu, 15 Mar 2018 10:51:03 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Greentime Hu <green.hu@...il.com>, Arnd Bergmann <arnd@...db.de>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Jesper Nilsson <jesper@....nu>
Subject: linux-next: manual merge of the nds32 tree with the asm-generic
 tree

Hi Greentime,

Today's linux-next merge of the nds32 tree got a conflict in:

  arch/cris/include/asm/io.h

between commit:

  77b0b77f7812 ("CRIS: Drop support for the CRIS port")

from the asm-generic tree and commit:

  c25a4f41b284 ("cris: add ioremap_nocache declaration before include asm-generic/io.h.")

from the nds32 tree.

I fixed it up (I just removed the file) 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

Content of type "application/pgp-signature" skipped