From: pr-tracker-bot@kernel.org
To: Trond Myklebust <trondmy@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org
Subject: Re: [GIT PULL] Please pull NFS client bugfixes for 6.17
Date: Wed, 10 Sep 2025 19:42:38 +0000 [thread overview]
Message-ID: <175753335865.1546567.12052545947146428602.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <150cb132accb448dd29e30af08394548b26524d5.camel@kernel.org>
The pull request you sent on Wed, 10 Sep 2025 14:34:55 -0400:
> git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.17-3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7aac71907bdea16e2754a782b9d9155449a9d49d
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
prev parent reply other threads:[~2025-09-10 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 18:34 [GIT PULL] Please pull NFS client bugfixes for 6.17 Trond Myklebust
2025-09-10 19:42 ` 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=175753335865.1546567.12052545947146428602.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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