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

Message-Id: <20211213222443.474487-1-broonie@kernel.org>
Date:   Mon, 13 Dec 2021 22:24:43 +0000
From:   broonie@...nel.org
To:     Matthew Wilcox <willy@...radead.org>,
        Shuah Khan <skhan@...uxfoundation.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        linux-kselftest@...r.kernel.org
Subject: linux-next: manual merge of the xarray tree with the kselftest tree

Hi all,

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

  tools/include/linux/kernel.h

between commits:

  d6e6a27d960f9 ("tools: Fix math.h breakage")
  066b34aa5461f ("tools: fix ARRAY_SIZE defines in tools and selftests hdrs")

from the kselftest and origin trees and commit:

  f2aa11fd51440 ("tools: Fix math.h breakage")

from the xarray 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 tools/include/linux/kernel.h
index 9701e8307db02,3e8df500cfbd4..0000000000000
--- a/tools/include/linux/kernel.h
+++ b/tools/include/linux/kernel.h