linux-kernel - linux-next: manual merge of the bitmap tree with the block 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: <20240221142051.4509d214@canb.auug.org.au>
Date: Wed, 21 Feb 2024 14:20:51 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Yury Norov <yury.norov@...il.com>, Jens Axboe <axboe@...nel.dk>
Cc: Christoph Hellwig <hch@....de>, 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 block tree

Hi all,

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

  drivers/block/null_blk/main.c

between commit:

  8b631f9cf0b8 ("null_blk: remove the bio based I/O path")

from the block tree and commit:

  f3687f2f7db4 ("block: null_blk: replace get_tag() with a generic find_and_set_bit_lock()")

from the bitmap tree.

I fixed it up (the former removed the code updated by the latter) 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