public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.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 09:25:57 -0500	[thread overview]
Message-ID: <ff54b6fb-6c82-4994-b9ff-715f9645d75c@kernel.org> (raw)
In-Reply-To: <2026010808-subwoofer-diabetic-e54e@gregkh>

On 1/8/26 6:03 AM, Greg Kroah-Hartman wrote:
> On Sat, Jan 03, 2026 at 02:38:51PM -0500, Chuck Lever wrote:
>> From: Chuck Lever <chuck.lever@oracle.com>
>>
>> [ Upstream commit 335a7be84b526861f3deb4fdd5d5c2a48cf1feef ]
> 
> I don't see this git id anywhere in Linus's tree, are you sure it is
> correct?
> 
> thanks,
> 
> greg k-h

If I start from the current upstream master, I find this instead:

commit 11fec9b9fb04fd1b3330a3b91ab9dcfa81ad5ad3
Author:     Jeff Layton <jlayton@kernel.org>
AuthorDate: Wed Oct 4 14:52:37 2023 -0400
Commit:     Christian Brauner <brauner@kernel.org>
CommitDate: Wed Oct 18 14:08:24 2023 +0200

    nfsd: convert to new timestamp accessors

    Convert to using the new inode timestamp accessor functions.

    Signed-off-by: Jeff Layton <jlayton@kernel.org>
    Link:
https://lore.kernel.org/r/20231004185347.80880-50-jlayton@kernel.org
    Signed-off-by: Christian Brauner <brauner@kernel.org>

I picked up 335a7be84b526861f3deb4fdd5d5c2a48cf1feef from an
nfsd-related tag by mistake. Do you want to drop this series and I can
rework it properly?


-- 
Chuck Lever

  reply	other threads:[~2026-01-08 14:25 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 [this message]
2026-01-08 15:27       ` Greg Kroah-Hartman
2026-01-08 12:33   ` Greg Kroah-Hartman
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=ff54b6fb-6c82-4994-b9ff-715f9645d75c@kernel.org \
    --to=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox