From: Mike-SPC via Bugspray Bot <bugbot@kernel.org>
To: neilb@ownmail.net, anna@kernel.org, linux-kernel@vger.kernel.org,
david.laight@aculab.com, linux-nfs@vger.kernel.org,
david.laight.linux@gmail.com, jlayton@kernel.org,
speedcracker@hotmail.com, stable@vger.kernel.org,
akpm@linux-foundation.org, cel@kernel.org, neil@brown.name,
trondmy@kernel.org, neilb@brown.name
Subject: Re: Compile Error fs/nfsd/nfs4state.o - clamp() low limit slotsize greater than high limit total_avail/scale_factor
Date: Sat, 15 Nov 2025 11:00:30 +0000 [thread overview]
Message-ID: <20251115-b220745c17-d79a0b4d3866@bugzilla.kernel.org> (raw)
In-Reply-To: <20251104-b220745c0-91170b3b3642@bugzilla.kernel.org>
Mike-SPC writes via Kernel.org Bugzilla:
Hi there,
at first: Thanks for patching and investigation.
I've tested the patch mentioned in
https://lkml.org/lkml/2025/11/10/12
and it works (for me).
Thanks again and regards,
Michael
View: https://bugzilla.kernel.org/show_bug.cgi?id=220745#c17
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
prev parent reply other threads:[~2025-11-15 11:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 14:15 Compile Error fs/nfsd/nfs4state.o - clamp() low limit slotsize greater than high limit total_avail/scale_factor Mike-SPC via Bugspray Bot
2025-11-04 14:50 ` Chuck Lever
2025-11-04 22:20 ` NeilBrown
2025-11-05 8:25 ` Mike-SPC via Bugspray Bot
2025-11-05 12:25 ` Mike-SPC via Bugspray Bot
2025-11-05 14:29 ` Chuck Lever
2025-11-06 11:30 ` Mike-SPC via Bugspray Bot
2025-11-06 12:29 ` Jeff Layton
2025-11-06 14:33 ` Fwd: " Chuck Lever
2025-11-06 19:22 ` David Laight
2025-11-06 19:32 ` Chuck Lever
2025-11-06 22:39 ` David Laight
2025-11-07 11:17 ` NeilBrown
2025-11-07 11:43 ` David Laight
2025-11-07 22:49 ` NeilBrown
2025-11-08 15:49 ` Chuck Lever
2025-11-08 22:40 ` David Laight
2025-11-15 11:00 ` Mike-SPC via Bugspray Bot [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=20251115-b220745c17-d79a0b4d3866@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=david.laight.linux@gmail.com \
--cc=david.laight@aculab.com \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=neilb@brown.name \
--cc=neilb@ownmail.net \
--cc=speedcracker@hotmail.com \
--cc=stable@vger.kernel.org \
--cc=trondmy@kernel.org \
/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).