From: Chuck Lever <cel@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-nfs@vger.kernel.org,
Jeff Layton <jlayton@kernel.org>
Subject: Re: [GIT PULL] NFSD changes for v6.16
Date: Wed, 28 May 2025 15:44:59 -0400 [thread overview]
Message-ID: <f5ddb28b-996e-4cbc-ad8d-c0af1c800e28@kernel.org> (raw)
In-Reply-To: <CAHk-=wggC6PP9ZNwKY7sEzdsC7h8qySA7pjqAchrYowniADUQg@mail.gmail.com>
On 5/28/25 3:38 PM, Linus Torvalds wrote:
> On Tue, 27 May 2025 at 07:17, <cel@kernel.org> wrote:
>>
>> NFSD 6.16 Release Notes
>
> Pulled - but I have a silly request.
>
> Can you fix your kernel.org email sending setup so that you have a
> real name, not just your login name?
Fixed, I think, in my ~/.gitconfig.
--
Chuck Lever
next prev parent reply other threads:[~2025-05-28 19:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 14:17 [GIT PULL] NFSD changes for v6.16 cel
2025-05-28 19:38 ` Linus Torvalds
2025-05-28 19:44 ` Chuck Lever [this message]
2025-05-28 20:18 ` Konstantin Ryabitsev
2025-05-28 20:35 ` Linus Torvalds
2025-05-28 19:44 ` pr-tracker-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=f5ddb28b-996e-4cbc-ad8d-c0af1c800e28@kernel.org \
--to=cel@kernel.org \
--cc=jlayton@kernel.org \
--cc=konstantin@linuxfoundation.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