From: Coly Li <colyli@suse.de>
To: Song Liu <song@kernel.org>, Mikulas Patocka <mpatocka@redhat.com>
Cc: Shen Lichuan <shenlichuan@vivo.com>,
Kent Overstreet <kent.overstreet@linux.dev>,
Alasdair Kergon <agk@redhat.com>,
snitzer@kernel.org, "yukuai (C)" <yukuai3@huawei.com>,
Bcache Linux <linux-bcache@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dm-devel@lists.linux.dev,
"Kernel.org-Linux-RAID" <linux-raid@vger.kernel.org>
Subject: Re: [PATCH v1] md: Correct typos in multiple comments across various files
Date: Wed, 25 Sep 2024 15:19:52 +0800 [thread overview]
Message-ID: <E9AFA16B-E8E4-4932-AC9F-A30BA1A8C924@suse.de> (raw)
In-Reply-To: <CAPhsuW51S=WfyNoP_cWvNVq3rPW0+iBrhzRVaKK=q3PLRA94UA@mail.gmail.com>
> 2024年9月25日 05:24，Song Liu <song@kernel.org> 写道：
>
> Hi Mikulas,
>
> On Tue, Sep 24, 2024 at 6:30 AM Mikulas Patocka <mpatocka@redhat.com> wrote:
>>
>> Hi
>>
>> I've applied the device mapper part of the patch.
>
> Would you mind taking the whole patch instead? You can add
>
> Acked-by: Song Liu <song@kernel.org>
Normally I don’t have interest for this type of patches, because it may introduce potential workload for downstream backport.
If this patch may go into upstream from other path, I don’t have objection neither. And if any comment wanted from me, I’d like to suggest to split this patch into multiple ones by different subsystem, it may be easier for downstream developers to do their backport.
Thanks.
Coly Li
next prev parent reply other threads:[~2024-09-25 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 9:17 [PATCH v1] md: Correct typos in multiple comments across various files Shen Lichuan
2024-09-24 13:23 ` Mikulas Patocka
2024-09-24 21:24 ` Song Liu
2024-09-25 7:19 ` Coly Li [this message]
2024-09-25 9:05 ` Mikulas Patocka
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=E9AFA16B-E8E4-4932-AC9F-A30BA1A8C924@suse.de \
--to=colyli@suse.de \
--cc=agk@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=shenlichuan@vivo.com \
--cc=snitzer@kernel.org \
--cc=song@kernel.org \
--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 NNTP newsgroup(s).