linux-kernel - linux-next: manual merge of the bitmap tree with the origin 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 for Android: free password hash cracker in your pocket

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

Message-Id: <20220222004702.3360917-1-broonie@kernel.org>
Date:   Tue, 22 Feb 2022 00:47:02 +0000
From:   broonie@...nel.org
To:     Yury Norov <yury.norov@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the bitmap tree with the origin tree

Hi all,

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

  arch/parisc/include/asm/bitops.h

between commit:

  47d8c15615c0a ("include: move find.h from asm_generic to linux")

from the origin tree and commit:

  a7c7d06a49d69 ("include: move find.h from asm_generic to linux")

from the bitmap 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/parisc/include/asm/bitops.h
index 56ffd260c669b,c7a9997ac9cbb..0000000000000
--- a/arch/parisc/include/asm/bitops.h
+++ b/arch/parisc/include/asm/bitops.h

(used mainline version)