linux-kernel - linux-next: manual merge of the xarray tree with the wireless-drivers-next 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]

Date:   Thu, 28 Jun 2018 14:59:00 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Matthew Wilcox <willy@...radead.org>,
        Kalle Valo <kvalo@...eaurora.org>,
        Wireless <linux-wireless@...r.kernel.org>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Johannes Berg <johannes@...solutions.net>
Subject: linux-next: manual merge of the xarray tree with the
 wireless-drivers-next tree

Hi all,

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

  lib/Kconfig.debug

between commit:

  0e2dc70e3d0d ("bitfield: add tests")

from the wireless-drivers-next tree and commit:

  d968f529e39f ("xarray: Add XArray load operation")

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.

-- 
Cheers,
Stephen Rothwell

diff --cc lib/Kconfig.debug
index f2be7503f87c,df1ea92d924c..000000000000
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@@ -1802,13 -1802,9 +1802,16 @@@ config TEST_BITMA
  
  	  If unsure, say N.
  
 +config TEST_BITFIELD
 +	tristate "Test bitfield functions at runtime"
 +	help
 +	  Enable this option to test the bitfield functions at boot.
 +
 +	  If unsure, say N.
 +
+ config TEST_XARRAY
+ 	tristate "Test the XArray code at runtime"
+ 
  config TEST_UUID
  	tristate "Test functions located in the uuid module at runtime"
  

Content of type "application/pgp-signature" skipped