[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <te64v6zwwor6jkco6uiu2zz7ern6ijhyu5okfvdz3bmj3w5qfp@mx4zdniwymqj>
Date: Thu, 9 May 2024 15:58:57 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Kuan-Wei Chiu <visitorckw@...il.com>, Jens Axboe <axboe@...nel.dk>,
Coly Li <colyli@...e.de>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>, Matthew Mirvish <matthew@...2.xyz>
Subject: Re: linux-next: manual merge of the refactor-heap tree with the
block tree
On Thu, May 09, 2024 at 03:27:45PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the refactor-heap tree got conflicts in:
>
> drivers/md/bcache/bset.c
> drivers/md/bcache/bset.h
> drivers/md/bcache/btree.c
> drivers/md/bcache/writeback.c
>
> between commit:
>
> 3a861560ccb3 ("bcache: fix variable length array abuse in btree_iter")
>
> from the block tree and commit:
>
> afa5721abaaa ("bcache: Remove heap-related macros and switch to generic min_heap")
>
> from the refactor-heap tree.
>
> Ok, these conflicts are too extensive, so I am dropping the refactor-heap
> tree for today. I suggest you all get together and sort something out.
Coli and Kuan, you guys will need to get this sorted out quick if we
want refactor-heap to make the merge window
Powered by blists - more mailing lists