From: Jens Axboe <axboe@kernel.dk>
To: Song Liu <song@kernel.org>, Yu Kuai <yukuai3@huawei.com>,
Li Nan <linan122@huawei.com>,
Nathan Chancellor <nathan@kernel.org>
Cc: linux-raid@vger.kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] md/md-llbitmap: Use DIV_ROUND_UP_SECTOR_T
Date: Wed, 10 Sep 2025 18:23:59 -0600 [thread overview]
Message-ID: <175755023939.60476.3963353529532795428.b4-ty@kernel.dk> (raw)
In-Reply-To: <20250910-llbitmap-fix-64-div-for-32-bit-v1-1-453a5c8e3e00@kernel.org>
On Wed, 10 Sep 2025 13:47:26 -0700, Nathan Chancellor wrote:
> When building for 32-bit platforms, there are several link (if builtin)
> or modpost (if a module) errors due to dividends of type 'sector_t' in
> DIV_ROUND_UP:
>
> arm-linux-gnueabi-ld: drivers/md/md-llbitmap.o: in function `llbitmap_resize':
> drivers/md/md-llbitmap.c:1017:(.text+0xae8): undefined reference to `__aeabi_uldivmod'
> arm-linux-gnueabi-ld: drivers/md/md-llbitmap.c:1020:(.text+0xb10): undefined reference to `__aeabi_uldivmod'
> arm-linux-gnueabi-ld: drivers/md/md-llbitmap.o: in function `llbitmap_end_discard':
> drivers/md/md-llbitmap.c:1114:(.text+0xf14): undefined reference to `__aeabi_uldivmod'
> arm-linux-gnueabi-ld: drivers/md/md-llbitmap.o: in function `llbitmap_start_discard':
> drivers/md/md-llbitmap.c:1097:(.text+0x1808): undefined reference to `__aeabi_uldivmod'
> arm-linux-gnueabi-ld: drivers/md/md-llbitmap.o: in function `llbitmap_read_sb':
> drivers/md/md-llbitmap.c:867:(.text+0x2080): undefined reference to `__aeabi_uldivmod'
> arm-linux-gnueabi-ld: drivers/md/md-llbitmap.o:drivers/md/md-llbitmap.c:895: more undefined references to `__aeabi_uldivmod' follow
>
> [...]
Applied, thanks!
[1/1] md/md-llbitmap: Use DIV_ROUND_UP_SECTOR_T
commit: 7935b843ce2184164f41c3b5c64e9f52994306f4
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-09-11 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 20:47 [PATCH] md/md-llbitmap: Use DIV_ROUND_UP_SECTOR_T Nathan Chancellor
2025-09-11 0:23 ` Jens Axboe [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=175755023939.60476.3963353529532795428.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=linan122@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=nathan@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