From: Yu Kuai <yukuai1@huaweicloud.com>
To: Jens Axboe <axboe@kernel.dk>, Yu Kuai <yukuai1@huaweicloud.com>,
linux-raid@vger.kernel.org, song@kernel.org
Cc: yangerkun@huawei.com, yi.zhang@huawei.com,
johnny.chenyi@huawei.com, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [GIT PULL] md-6.16-20250512
Date: Tue, 13 May 2025 10:13:51 +0800 [thread overview]
Message-ID: <a7f83029-a46a-e59b-8841-5ed67a1a0034@huaweicloud.com> (raw)
In-Reply-To: <4df296d5-e6cb-4d11-9d47-76d38a442d24@kernel.dk>
Hi,
在 2025/05/13 10:01, Jens Axboe 写道:
> On 5/12/25 7:38 PM, Yu Kuai wrote:
>> Hi Jens,
>>
>> Please consider pulling following changes for md-6.6 on your for-6.16/block
>> branch, this pull request contains:
>>
>> - fix normal IO can be starved by sync IO, found by mkfs on newly created
>> large raid5, with some clean up patches for bdev inflight counters;
>> - add kconfig for md-bitmap, I have decided not to continue optimizing
>> based on the old bitmap implementation, and plan to invent a new lock-less
>> bitmap. And a new kconfig option is a good way for isolation;
>
> Pulled, and then unpulled. This doesn't even build...
>
> ERROR: modpost: "md_bitmap_exit" [drivers/md/md-mod.ko] undefined!
> ERROR: modpost: "md_bitmap_init" [drivers/md/md-mod.ko] undefined!
> make[2]: *** [scripts/Makefile.modpost:147: Module.symvers] Error 1
> make[1]: *** [/home/axboe/git/build/Makefile:1954: modpost] Error 2
> make: *** [Makefile:248: __sub-make] Error 2
>
> Before you send out pull requests, at least ensure that it builds
> both built-in and modular.
My apologize for this, the v3 patchset have this problem and Paul
reported to me, fix it in v4 however, It's a long time and somehow
I picked the v3 set here. :(
Thanks,
Kuai
>
prev parent reply other threads:[~2025-05-13 2:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 1:38 [GIT PULL] md-6.16-20250512 Yu Kuai
2025-05-13 2:01 ` Jens Axboe
2025-05-13 2:13 ` Yu Kuai [this message]
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=a7f83029-a46a-e59b-8841-5ed67a1a0034@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=johnny.chenyi@huawei.com \
--cc=linux-raid@vger.kernel.org \
--cc=song@kernel.org \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.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 NNTP newsgroup(s).