From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Chuck Lever <cel@kernel.org>
Cc: stable@vger.kernel.org, linux-nfs@vger.kernel.org,
Sasha Levin <sashal@kernel.org>,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH 6.6.y 1/4] nfsd: convert to new timestamp accessors
Date: Thu, 8 Jan 2026 13:33:38 +0100 [thread overview]
Message-ID: <2026010810-obsessed-superior-9b56@gregkh> (raw)
In-Reply-To: <20260103193854.2954342-2-cel@kernel.org>
On Sat, Jan 03, 2026 at 02:38:51PM -0500, Chuck Lever wrote:
> From: Chuck Lever <chuck.lever@oracle.com>
>
> [ Upstream commit 335a7be84b526861f3deb4fdd5d5c2a48cf1feef ]
>
> [ cel: adjust to the 6.6.y version of fs/nfsd/blocklayout.c ]
> Stable-dep-of: 24d92de9186e ("nfsd: Fix NFSv3 atomicity bugs in nfsd_setattr()")
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> ---
Is this really commit 11fec9b9fb04 ("nfsd: convert to new timestamp
accessors")? if so, what happened to the original authorship and other
signed-off-by lines?
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-08 12:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-03 19:38 [PATCH 6.6.y 0/4] NFSD: NFSv4 file creation neglects setting ACL Chuck Lever
2026-01-03 19:38 ` [PATCH 6.6.y 1/4] nfsd: convert to new timestamp accessors Chuck Lever
2026-01-08 11:03 ` Greg Kroah-Hartman
2026-01-08 14:25 ` Chuck Lever
2026-01-08 15:27 ` Greg Kroah-Hartman
2026-01-08 12:33 ` Greg Kroah-Hartman [this message]
2026-01-03 19:38 ` [PATCH 6.6.y 2/4] nfsd: Fix NFSv3 atomicity bugs in nfsd_setattr() Chuck Lever
2026-01-03 19:38 ` [PATCH 6.6.y 3/4] nfsd: set security label during create operations Chuck Lever
2026-01-03 19:38 ` [PATCH 6.6.y 4/4] NFSD: NFSv4 file creation neglects setting ACL Chuck Lever
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=2026010810-obsessed-superior-9b56@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.