From: Chuck Lever via Bugspray Bot <bugbot@kernel.org>
To: linux-nfs@vger.kernel.org, cel@kernel.org, aglo@umich.edu,
trondmy@kernel.org, anna@kernel.org, jlayton@kernel.org
Subject: Re: warning in nfsd4_cb_done
Date: Tue, 04 Feb 2025 13:30:12 +0000 [thread overview]
Message-ID: <20250204-b219737c8-56e36733bccb@bugzilla.kernel.org> (raw)
In-Reply-To: <20250204-b219737c7-947e192554be@bugzilla.kernel.org>
Chuck Lever writes via Kernel.org Bugzilla:
(In reply to rik.theys from comment #7)
> Is it possible this patch has not (yet) been sent to stable@vger.kernel.org
> so it ends up in 6.12.y?
Commit 1b3e26a5ccbf has been in a publicly released kernel for exactly two days (as of this writing). It will take some time before it appears in any LTS kernel. For now, if you would like to test the commit, you need to apply it manually.
View: https://bugzilla.kernel.org/show_bug.cgi?id=219737#c8
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2025-02-04 13:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 14:05 warning in nfsd4_cb_done rik.theys via Bugspray Bot
2025-01-30 14:10 ` Chuck Lever via Bugspray Bot
2025-01-30 15:08 ` Olga Kornievskaia
2025-01-30 15:20 ` Chuck Lever via Bugspray Bot
2025-01-30 15:20 ` Chuck Lever via Bugspray Bot
2025-01-30 15:55 ` Chuck Lever via Bugspray Bot
2025-01-30 14:20 ` rik.theys via Bugspray Bot
2025-02-04 13:30 ` rik.theys via Bugspray Bot
2025-02-04 13:30 ` Chuck Lever via Bugspray Bot [this message]
2025-02-10 15:03 ` Olga Kornievskaia
2025-02-10 16:35 ` Jeff Layton via Bugspray Bot
2025-02-10 15:45 ` Jeff Layton via Bugspray Bot
2025-02-10 16:45 ` Chuck Lever via Bugspray Bot
2025-02-24 11:55 ` rik.theys via Bugspray Bot
2025-02-24 12:20 ` Jeff Layton via Bugspray Bot
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=20250204-b219737c8-56e36733bccb@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=aglo@umich.edu \
--cc=anna@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-nfs@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