All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Begunkov <asml.silence@gmail.com>
To: Daniele Salvatore Albano <d.albano@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, io-uring <io-uring@vger.kernel.org>
Subject: Re: [PATCH liburing 1/1] update rsrc register/update ABI and tests
Date: Thu, 10 Jun 2021 20:24:53 +0100	[thread overview]
Message-ID: <af61981e-6c3b-bc1c-543d-14358f451917@gmail.com> (raw)
In-Reply-To: <CAKq9yRiQ2P+iggjOPD7fDSXY6GDOX7M_Aw8dyw--QKBvOrwHFw@mail.gmail.com>

On 6/10/21 8:10 PM, Daniele Salvatore Albano wrote:
> On Thu, 10 Jun 2021 at 18:42, Pavel Begunkov <asml.silence@gmail.com> wrote:
>>
>> There is an ABI change for not yet released buffer/files
>> registration/update tagging/etc. support. Update the bits.
>>
>> Signed-off-by: Pavel Begunkov <asml.silence@gmail.com>
>> ---
>>  src/include/liburing/io_uring.h | 20 +++++++-------
>>  test/rsrc_tags.c                | 46 ++++++++++++++++++++-------------
>>  2 files changed, 38 insertions(+), 28 deletions(-)
>>
>> diff --git a/src/include/liburing/io_uring.h b/src/include/liburing/io_uring.h
>> index 5a3cb90..4c5685d 100644
>> --- a/src/include/liburing/io_uring.h
>> +++ b/src/include/liburing/io_uring.h
>> @@ -141,7 +141,6 @@ enum {
>>         IORING_OP_SHUTDOWN,
>>         IORING_OP_RENAMEAT,
>>         IORING_OP_UNLINKAT,
>> -       IORING_OP_MKDIRAT,
> 
> Is dropping IORING_OP_MKDIRAT intentionally part of the patch?

Good catch, it is not. However, IORING_OP_MKDIRAT is not
supported yet anyway, so I don't actually care much

-- 
Pavel Begunkov

      reply	other threads:[~2021-06-10 19:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10 15:40 [PATCH liburing 1/1] update rsrc register/update ABI and tests Pavel Begunkov
2021-06-10 19:10 ` Daniele Salvatore Albano
2021-06-10 19:24   ` Pavel Begunkov [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=af61981e-6c3b-bc1c-543d-14358f451917@gmail.com \
    --to=asml.silence@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=d.albano@gmail.com \
    --cc=io-uring@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 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.