From: Jens Axboe <axboe@kernel.dk>
To: David Howells <dhowells@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Vishal Moola (Oracle)" <vishal.moola@gmail.com>
Subject: Re: linux-next: manual merge of the block tree with the mm tree
Date: Fri, 16 Jun 2023 10:07:36 -0600 [thread overview]
Message-ID: <dded1115-c7e1-486f-2564-a5c6ea013bcd@kernel.dk> (raw)
In-Reply-To: <424129.1686909362@warthog.procyon.org.uk>
On 6/16/23 3:56?AM, David Howells wrote:
> Andrew Morton <akpm@linux-foundation.org> wrote:
>
>> That's getting a bit nasty. Maybe David's patches are in the wrong
>> tree.
>
> You'd need to discuss that one with Jens. The patches you'd have to
> transfer also touch a number of block-related files. Looking at
> block/for-next, there don't seem to be many other patches touching
> those files, but I've seen patches from Christoph that will need to be
> applied on top of mine.
It's definitely a bit of a mess now, but for-6.5/block also depends on
these changes and make further tweaks on the block front.
for-6.5/splice is stable, so just pull that in?
--
Jens Axboe
next prev parent reply other threads:[~2023-06-16 16:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 1:58 linux-next: manual merge of the block tree with the mm tree Stephen Rothwell
2023-06-16 3:50 ` Andrew Morton
2023-06-16 9:56 ` David Howells
2023-06-16 16:07 ` Jens Axboe [this message]
2023-06-16 19:44 ` Vishal Moola
-- strict thread matches above, loose matches on Subject: below --
2026-10-20 12:27 Mark Brown
2026-10-20 12:45 ` Jens Axboe
2026-10-20 17:00 ` Andrew Morton
2026-10-20 17:13 ` Jens Axboe
2026-10-20 18:43 ` Andrew Morton
2024-04-02 0:27 Stephen Rothwell
2024-05-13 23:41 ` Stephen Rothwell
2024-05-13 23:43 ` Edgecombe, Rick P
2024-02-14 0:25 Stephen Rothwell
2024-03-11 21:54 ` Stephen Rothwell
2023-06-16 1:50 Stephen Rothwell
2023-03-22 23:02 Stephen Rothwell
2023-03-22 23:13 ` David Howells
2023-03-22 23:15 ` Jens Axboe
2023-03-22 23:26 ` Andrew Morton
2023-03-23 0:03 ` Stephen Rothwell
2023-03-23 0:04 ` David Howells
2023-03-23 0:49 ` Jens Axboe
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=dded1115-c7e1-486f-2564-a5c6ea013bcd@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=vishal.moola@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.