From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kent Overstreet <kent.overstreet@linux.dev>,
Kuan-Wei Chiu <visitorckw@gmail.com>,
Jens Axboe <axboe@kernel.dk>
Cc: Coly Li <colyli@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Matthew Mirvish <matthew@mm12.xyz>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: manual merge of the refactor-heap tree with the block tree
Date: Tue, 28 May 2024 11:07:37 +1000 [thread overview]
Message-ID: <20240528110737.730a8f40@canb.auug.org.au> (raw)
In-Reply-To: <20240509152745.08af752f@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 990 bytes --]
Hi all,
On Thu, 9 May 2024 15:27:45 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> 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.
It looks as though the patches from the refactor-heap tree are now being
carried in the mm-nonmm-unstable branch of the mm tree. Should I
rmeove the refactor-heap tree from linux-next? It *will* be dropped for
today at least.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-05-28 1:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 5:27 linux-next: manual merge of the refactor-heap tree with the block tree Stephen Rothwell
2024-05-09 19:58 ` Kent Overstreet
2024-05-09 22:44 ` Kuan-Wei Chiu
2024-05-09 23:16 ` Kent Overstreet
2024-05-10 3:07 ` Kuan-Wei Chiu
2024-05-10 3:46 ` Matthew Mirvish
2024-05-10 9:10 ` Kuan-Wei Chiu
2024-05-11 19:24 ` Kuan-Wei Chiu
2024-05-14 7:40 ` Bagas Sanjaya
2024-05-21 2:18 ` Stephen Rothwell
2024-05-21 2:44 ` Kuan-Wei Chiu
2024-05-21 13:42 ` Kent Overstreet
2024-05-28 1:07 ` Stephen Rothwell [this message]
2024-05-28 1:18 ` Kent Overstreet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240528110737.730a8f40@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=colyli@suse.de \
--cc=kent.overstreet@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthew@mm12.xyz \
--cc=visitorckw@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.