All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	Stefan Roesch <shr@fb.com>,
	kernel-team@fb.com
Cc: viro@zeniv.linux.org.uk, christian.brauner@ubuntu.com
Subject: Re: [PATCH v13 0/4] io_uring: add xattr support
Date: Wed, 30 Mar 2022 14:27:43 -0600	[thread overview]
Message-ID: <164867206347.288397.17239948549986263927.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220323154420.3301504-1-shr@fb.com>

On Wed, 23 Mar 2022 08:44:16 -0700, Stefan Roesch wrote:
> This adds the xattr support to io_uring. The intent is to have a more
> complete support for file operations in io_uring.
> 
> This change adds support for the following functions to io_uring:
> - fgetxattr
> - fsetxattr
> - getxattr
> - setxattr
> 
> [...]

Applied, thanks!

[1/4] fs: split off setxattr_copy and do_setxattr function from setxattr
      commit: bbe6239e931bbb57983dcf94eacc8aaa757d26b0
[2/4] fs: split off do_getxattr from getxattr
      commit: 9c8ebeb51e866b9d0fa16fa628797d7e9483a6fc
[3/4] io_uring: add fsetxattr and setxattr support
      commit: 7c0773d493344a03e40a71c66fbe080c1fd87acb
[4/4] io_uring: add fgetxattr and getxattr support
      commit: b2fdcc6667b89e4da68b5543b641e809145432f8

Best regards,
-- 
Jens Axboe



      parent reply	other threads:[~2022-03-30 20:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-23 15:44 [PATCH v13 0/4] io_uring: add xattr support Stefan Roesch
2022-03-23 15:44 ` [PATCH v13 1/4] fs: split off setxattr_copy and do_setxattr function from setxattr Stefan Roesch
2022-03-23 15:44 ` [PATCH v13 2/4] fs: split off do_getxattr from getxattr Stefan Roesch
2022-03-23 15:44 ` [PATCH v13 3/4] io_uring: add fsetxattr and setxattr support Stefan Roesch
2022-03-23 15:44 ` [PATCH v13 4/4] io_uring: add fgetxattr and getxattr support Stefan Roesch
2022-03-24  8:50   ` Christian Brauner
2022-03-30 20:27 ` Jens Axboe [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=164867206347.288397.17239948549986263927.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=christian.brauner@ubuntu.com \
    --cc=io-uring@vger.kernel.org \
    --cc=kernel-team@fb.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=shr@fb.com \
    --cc=viro@zeniv.linux.org.uk \
    /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.