From: Jens Axboe <axboe@kernel.dk>
To: Yu Kuai <hailan@yukuai.org.cn>, Yu Kuai <yukuai1@huaweicloud.com>,
linux-block@vger.kernel.org, inux-raid@vger.kernel.org,
song@kernel.org
Cc: linan122@huawei.com, xni@redhat.com, colyli@kernel.org,
yukuai3@huawei.com, yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com
Subject: Re: [GIT PULL] md-6.17-20250909
Date: Tue, 9 Sep 2025 10:51:18 -0600 [thread overview]
Message-ID: <16a63a35-9a44-443a-8f59-e60afbfbfff3@kernel.dk> (raw)
In-Reply-To: <fdfcb000-916b-4599-b75c-1b4680accca7@yukuai.org.cn>
On 9/9/25 10:44 AM, Yu Kuai wrote:
> Hi,
>
> ? 2025/9/9 21:26, Jens Axboe ??:
>> On 9/9/25 2:20 AM, Yu Kuai wrote:
>>> Hi, Jens
>>>
>>> Please consider pulling following changes on your for-6.18/block branch,
>>> this pull request contains:
>>>
>>> - add kconfig for internal bitmap;
>>> - introduce new experimental feature lockless bitmap;
>> Can you write a bit of a better pull request letter? It'd be nice to get
>> an actual description of what the "lockless bitmap" is, and why it makes
>> sense to have it. This is pretty sparse...
>
> Of course, details in be found in the patch 0 of the thread. I'll send a v2.
Please always write a decent message on why any pull request needs
merging.
>>> https://kernel.googlesource.com/pub/scm/linux/kernel/git/mdraid/linux.git tags/md-6.18-20250909
>>>
>> and this is a new source for you, is the above tag signed?
>
> I thought they are the same, I'll switch back in v2.
They are very much NOT the same. One is some random site, the other is
the official kernel infrastructure. If you don't use git.kernel.org,
I'm definitely not pulling anything that isn't signed by a key, and
that key in turn has been signed by other people I know.
--
Jens Axboe
next prev parent reply other threads:[~2025-09-09 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 8:20 [GIT PULL] md-6.17-20250909 Yu Kuai
2025-09-09 8:31 ` Yu Kuai
2025-09-09 13:26 ` Jens Axboe
2025-09-09 16:44 ` Yu Kuai
2025-09-09 16:51 ` Jens Axboe [this message]
2025-09-09 16:54 ` Jens Axboe
2025-09-09 17:09 ` 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=16a63a35-9a44-443a-8f59-e60afbfbfff3@kernel.dk \
--to=axboe@kernel.dk \
--cc=colyli@kernel.org \
--cc=hailan@yukuai.org.cn \
--cc=inux-raid@vger.kernel.org \
--cc=johnny.chenyi@huawei.com \
--cc=linan122@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=song@kernel.org \
--cc=xni@redhat.com \
--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