From: Matthew Sakai <msakai@redhat.com>
To: Yu Kuai <yukuai1@huaweicloud.com>,
Christian Brauner <brauner@kernel.org>
Cc: jack@suse.cz, hch@lst.de, axboe@kernel.dk,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
"yukuai (C)" <yukuai3@huawei.com>,
dm-devel@lists.linux.dev
Subject: Re: [RFC v4 linux-next 00/19] fs & block: remove bdev->bd_inode
Date: Mon, 18 Mar 2024 22:13:23 -0400 [thread overview]
Message-ID: <0665f6a6-39d9-e730-9403-0348c181dd55@redhat.com> (raw)
In-Reply-To: <dd4e443a-696d-b02f-44ff-4649b585ef17@huaweicloud.com>
On 3/18/24 21:43, Yu Kuai wrote:
> Hi,
>
> 在 2024/03/19 9:18, Yu Kuai 写道:
>> Hi,
>>
>> 在 2024/03/18 17:39, Christian Brauner 写道:
>>> On Sat, Mar 16, 2024 at 10:49:33AM +0800, Yu Kuai wrote:
>>>> Hi, Christian
>>>>
>>>> 在 2024/03/15 21:54, Christian Brauner 写道:
>>>>> On Fri, Mar 15, 2024 at 08:08:49PM +0800, Yu Kuai wrote:
>>>>>> Hi, Christian
>>>>>> Hi, Christoph
>>>>>> Hi, Jan
>>>>>>
>>>>>> Perhaps now is a good time to send a formal version of this set.
>>>>>> However, I'm not sure yet what branch should I rebase and send
>>>>>> this set.
>>>>>> Should I send to the vfs tree?
>>>>>
>>>>> Nearly all of it is in fs/ so I'd say yes.
>>>>> .
>>>>
>>>> I see that you just create a new branch vfs.fixes, perhaps can I rebase
>>>> this set against this branch?
>>>
>>> Please base it on vfs.super. I'll rebase it to v6.9-rc1 on Sunday.
>>
>> Okay, I just see that vfs.super doesn't contain commit
>> 1cdeac6da33f("btrfs: pass btrfs_device to btrfs_scratch_superblocks()"),
>> and you might need to fix the conflict at some point.
>
> And there is another problem, dm-vdo doesn't exist in vfs.super yet. Do
> you still want me to rebase here?
>
The dm-vdo changes don't appear to rely on earlier patches in the
series, so I think dm-vdo could incorporate the dm-vdo patch
independently from the rest of the series, if that would be helpful. (I
don't want to confuse things too much.) In that case it would go through
the dm tree with the rest of dm-vdo.
Matt
next parent reply other threads:[~2024-03-19 2:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240222124555.2049140-1-yukuai1@huaweicloud.com>
[not found] ` <1324ffb5-28b6-34fb-014e-3f57df714095@huawei.com>
[not found] ` <20240315-assoziieren-hacken-b43f24f78970@brauner>
[not found] ` <ac0eb132-c604-9761-bce5-69158e73f256@huaweicloud.com>
[not found] ` <20240318-mythisch-pittoresk-1c57af743061@brauner>
[not found] ` <c9bfba49-9611-c965-713c-1ef0b1e305ce@huaweicloud.com>
[not found] ` <dd4e443a-696d-b02f-44ff-4649b585ef17@huaweicloud.com>
2024-03-19 2:13 ` Matthew Sakai [this message]
2024-03-19 2:27 ` [RFC v4 linux-next 00/19] fs & block: remove bdev->bd_inode Yu Kuai
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=0665f6a6-39d9-e730-9403-0348c181dd55@redhat.com \
--to=msakai@redhat.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).