From: pr-tracker-bot@kernel.org
To: cel@kernel.org
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: Re: [GIT PULL] 2nd round of NFSD fixes for v6.15
Date: Sat, 26 Apr 2025 17:54:19 +0000 [thread overview]
Message-ID: <174569005973.4037932.7521780680972977613.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20250426160531.5466-1-cel@kernel.org>
The pull request you sent on Sat, 26 Apr 2025 12:05:31 -0400:
> https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git tags/nfsd-6.15-2
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d22aad29de2a7b13f43ccb9b55cfd5daf793ead4
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2025-04-26 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 16:05 [GIT PULL] 2nd round of NFSD fixes for v6.15 cel
2025-04-26 17:54 ` pr-tracker-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=174569005973.4037932.7521780680972977613.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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