From: "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de>
To: Frank van der Linden <fllinden@amazon.com>
Cc: Anna Schumaker <anna.schumaker@netapp.com>,
linux-nfs <linux-nfs@vger.kernel.org>,
Trond Myklebust <trond.myklebust@hammerspace.com>
Subject: Re: [PATCH v2 00/13] NFS client user xattr (RFC8276) support
Date: Mon, 8 Jun 2020 18:52:15 +0200 (CEST) [thread overview]
Message-ID: <1285470887.979001.1591635135066.JavaMail.zimbra@desy.de> (raw)
In-Reply-To: <20200608164742.GA14076@dev-dsk-fllinden-2c-c1893d73.us-west-2.amazon.com>
Hi Frank,
----- Original Message -----
> From: "Frank van der Linden" <fllinden@amazon.com>
> To: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
> Cc: "Anna Schumaker" <anna.schumaker@netapp.com>, "linux-nfs" <linux-nfs@vger.kernel.org>, "Trond Myklebust"
> <trond.myklebust@hammerspace.com>
> Sent: Monday, June 8, 2020 6:47:42 PM
> Subject: Re: [PATCH v2 00/13] NFS client user xattr (RFC8276) support
> On Mon, Jun 08, 2020 at 06:37:29PM +0200, Mkrtchyan, Tigran wrote:
>> Thanks for clarification.
>>
>> Tigran.
>>
>> ----- Original Message -----
>> > From: "Anna Schumaker" <anna.schumaker@netapp.com>
>> > To: "Tigran Mkrtchyan" <tigran.mkrtchyan@desy.de>
>> > Cc: "linux-nfs" <linux-nfs@vger.kernel.org>, "Trond Myklebust"
>> > <trond.myklebust@hammerspace.com>, "Frank van der Linden"
>> > <fllinden@amazon.com>
>> > Sent: Monday, June 8, 2020 6:15:06 PM
>> > Subject: Re: [PATCH v2 00/13] NFS client user xattr (RFC8276) support
>>
>> > Hi Tigran,
>> >
>> >
>> > On Mon, Jun 8, 2020 at 11:59 AM Mkrtchyan, Tigran
>> > <tigran.mkrtchyan@desy.de> wrote:
>> >>
>> >>
>> >> Dear maintainers,
>> >>
>> >> are those changes considered for 5.8?
>> >
>> > My understanding is that these patches will be targeting 5.9.
>> >
>> > Anna
>
> Hi Tigran,
>
> Since there is one remaining open issue on the server side changes that needs
> signoff from the general fs maintainers, I agreed with Bruce & Chuck to target
> 5.9, as the 5.8 merge window is currently already open, and all the activity
> is centered around it.
>
> For the client side, there are no open issues that were flagged, so from my
> side it's all ready to go - except for me to post a v3 rebased to
> the latest tree, which is easy to do.
>
> In other words, I think it's ok for the client side to go in to 5.8, but it
> probably makes more sense to have it go in to the same version as the server
> side, so that's what I proposed to Anna & Trond.
Makes sense.
Thanks,
Tigran.
>
> - Frank
prev parent reply other threads:[~2020-06-08 16:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 23:10 [PATCH v2 00/13] NFS client user xattr (RFC8276) support Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 01/13] nfs,nfsd: NFSv4.2 extended attribute protocol definitions Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 02/13] nfs: add client side only definitions for user xattrs Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 03/13] NFSv4.2: define limits and sizes for user xattr handling Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 04/13] NFSv4.2: query the server for extended attribute support Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 05/13] NFSv4.2: add client side XDR handling for extended attributes Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 06/13] nfs: define nfs_access_get_cached function Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 07/13] NFSv4.2: query the extended attribute access bits Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 08/13] nfs: modify update_changeattr to deal with regular files Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 09/13] nfs: define and use the NFS_INO_INVALID_XATTR flag Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 10/13] nfs: make the buf_to_pages_noslab function available to the nfs code Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 11/13] NFSv4.2: add the extended attribute proc functions Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 12/13] NFSv4.2: hook in the user extended attribute handlers Frank van der Linden
2020-03-25 23:10 ` [PATCH v2 13/13] NFSv4.2: add client side xattr caching Frank van der Linden
2020-03-26 19:03 ` [PATCH v2 00/13] NFS client user xattr (RFC8276) support Mkrtchyan, Tigran
2020-03-26 19:43 ` Frank van der Linden
2020-03-26 23:16 ` Frank van der Linden
2020-03-27 7:51 ` Mkrtchyan, Tigran
[not found] ` <v2aze7-yqvuvfuc4i30-1xxisr-dr39sbpkxym7-2nbcltx37gs3ezoql-qoc5f45hvih45iurdv-lqtdu9ppbm6i-upakk-2awl3v-em4ktl4ip5gchvuicg-vgnve1-wbqe5p-fw96bj-ct2sjj-wlbpk7.1586002736523@email.android.com>
2020-06-08 15:52 ` Mkrtchyan, Tigran
2020-06-08 16:15 ` Anna Schumaker
2020-06-08 16:37 ` Mkrtchyan, Tigran
2020-06-08 16:47 ` Frank van der Linden
2020-06-08 16:52 ` Mkrtchyan, Tigran [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=1285470887.979001.1591635135066.JavaMail.zimbra@desy.de \
--to=tigran.mkrtchyan@desy.de \
--cc=anna.schumaker@netapp.com \
--cc=fllinden@amazon.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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;
as well as URLs for NNTP newsgroup(s).