Linux NFS development
 help / color / mirror / Atom feed
From: Scott Haiden <scott.b.haiden@gmail.com>
To: scott.b.haiden@gmail.com
Cc: linux-nfs@vger.kernel.org, trondmy@kernel.org
Subject: Re: [PATCH 0/4] More server capability fixes
Date: Mon, 8 Sep 2025 20:35:31 -0700	[thread overview]
Message-ID: <f8437b42-63b4-4f8d-b82e-0ff8cc540fb0@gmail.com> (raw)
In-Reply-To: <3e19b7e9-c3d2-43b5-96ea-c5cf7904e8a3@gmail.com>

Hello again,

I saw that these patches were marked in patchwork 
(https://patchwork.kernel.org/project/linux-nfs/list/?series=996999&state=*) 
as "handled elsewhere"; could I ask for a link to where they're handled? 
I tried looking at a few other patchsets in the nfs mailing list but I'm 
not that familiar with the NFS source and didn't see any that jumped out 
at me.

I'm hoping to follow the patch so I know when it's safe for me to update 
my kernel again.

Thanks!
--Scott


      reply	other threads:[~2025-09-09  3:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-29  3:46 [REGRESSION]: NFS 4.2 reports "Operation Not Supported" on getxattr calls Scott Haiden
2025-08-29  3:59 ` Scott Haiden
2025-08-29 16:57 ` [PATCH 0/4] More server capability fixes Trond Myklebust
2025-08-29 16:57   ` [PATCH 1/4] NFSv4: Don't clear capabilities that won't be reset Trond Myklebust
2025-08-29 16:57   ` [PATCH 2/4] NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set Trond Myklebust
2025-08-29 16:57   ` [PATCH 3/4] NFSv4: Clear NFS_CAP_OPEN_XOR and NFS_CAP_DELEGTIME if not supported Trond Myklebust
2025-08-29 16:57   ` [PATCH 4/4] NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server Trond Myklebust
2025-08-29 19:21   ` [PATCH 0/4] More server capability fixes Scott Haiden
2025-09-09  3:35     ` Scott Haiden [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=f8437b42-63b4-4f8d-b82e-0ff8cc540fb0@gmail.com \
    --to=scott.b.haiden@gmail.com \
    --cc=linux-nfs@vger.kernel.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