linux-kernel - linux-next: manual merge of the microblaze 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: <20201210105711.4cbb3b01@canb.auug.org.au>
Date:   Thu, 10 Dec 2020 10:57:11 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Michal Simek <monstr@...str.eu>, Arnd Bergmann <arnd@...db.de>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Michal Simek <michal.simek@...inx.com>,
        Nicholas Piggin <npiggin@...il.com>
Subject: linux-next: manual merge of the microblaze tree with the
 asm-generic tree

Hi all,

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

  arch/microblaze/include/asm/mmu_context.h

between commit:

  94f89922e1e0 ("asm-generic: add generic MMU versions of mmu context functions")

from the asm-generic tree and commit:

  05cdf457477d ("microblaze: Remove noMMU code")

from the microblaze tree.

I fixed it up (I just used the latter version) 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