Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Christian Brauner <brauner@kernel.org>, Chuck Lever <cel@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-kernel@vger.kernel.org,  linux-nfs@vger.kernel.org
Subject: Re: [GIT PULL] NFSD changes for v6.18
Date: Tue, 07 Oct 2025 07:47:39 -0400	[thread overview]
Message-ID: <39f56bc6833c6e25ac94cce6eba8eec3267ab5f6.camel@kernel.org> (raw)
In-Reply-To: <20251007-zoodirektor-widder-27776d2e7228@brauner>

On Tue, 2025-10-07 at 13:26 +0200, Christian Brauner wrote:
> On Mon, Oct 06, 2025 at 04:58:22PM -0400, Chuck Lever wrote:
> > On 10/6/25 4:51 PM, Linus Torvalds wrote:
> > > On Mon, 6 Oct 2025 at 06:50, Chuck Lever <cel@kernel.org> wrote:
> > > > 
> > > > One potential merge conflict has been reported for nfsd-6.18.
> > > 
> > > No problem, this is the simple kind of explicit conflict (famous last
> > > words before I mess one of those things up).
> > > 
> > > Anyway, the reason I'm replying is actually that I notice that you
> > > added that ATTR_CTIME_SET flag in <linux/fs.h> in commit afc5b36e29b9
> > > ("vfs: add ATTR_CTIME_SET flag").
> > > 
> > > No complaints about it, but it looks a bit odd with ATTR_{A,M}TIME_SET
> > > in bits 7 and 8, and then the new ATTR_CTIME_SET is in bit 10 with the
> > > entirely unrelated ATTR_FORCE in between them all.
> > 
> > Oof. We should have gotten Acks for "vfs: add ATTR_CTIME_SET flag". My
> > bad.
> 
> Yes, indeed. I wondered why I hadn't seen this patch.
> 

I did send it to fsdevel, but you may have missed it in the deluge. Mea
culpa from me too -- I should have noticed that you guys hadn't acked
this yet. Any objection?
-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-10-07 11:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 13:50 [GIT PULL] NFSD changes for v6.18 Chuck Lever
2025-10-06 20:51 ` Linus Torvalds
2025-10-06 20:58   ` Chuck Lever
2025-10-07 11:26     ` Christian Brauner
2025-10-07 11:47       ` Jeff Layton [this message]
2025-10-07 12:06         ` Christian Brauner
2025-10-06 21:20   ` Johannes Berg
2025-10-06 21:54     ` Linus Torvalds
2025-10-06 21:00 ` pr-tracker-bot
2025-10-13 10:15 ` Geert Uytterhoeven
2025-10-13 19:21   ` Eric Biggers
2025-10-13 19:37     ` Chuck Lever
2025-10-16 14:31       ` Jeff Layton
2025-10-16 14:36         ` Geert Uytterhoeven
2025-10-16 15:04           ` Chuck Lever
2025-10-16 15:19             ` Trond Myklebust
2025-10-16 18:02               ` Eric Biggers
2025-10-16 18:09                 ` 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=39f56bc6833c6e25ac94cce6eba8eec3267ab5f6.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=brauner@kernel.org \
    --cc=cel@kernel.org \
    --cc=johannes@sipsolutions.net \
    --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