public inbox for fio@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Minwoo Im <minwoo.im.dev@gmail.com>, fio@vger.kernel.org
Cc: Vincent Fu <vincent.fu@samsung.com>, Minwoo Im <minwoo.im@samsung.com>
Subject: Re: [PATCH] io_uring: Add IO_U_F_DEVICE_ERROR to identify error types
Date: Thu, 26 Sep 2024 11:48:22 -0600	[thread overview]
Message-ID: <1c383a92-ea5c-485f-9015-995c77117dfe@kernel.dk> (raw)
In-Reply-To: <20240926004134.26004-1-minwoo.im.dev@gmail.com>

On 9/25/24 6:41 PM, Minwoo Im wrote:
> diff --git a/io_u.h b/io_u.h
> index ab93d50f967e..20afad667ee1 100644
> --- a/io_u.h
> +++ b/io_u.h
> @@ -22,6 +22,7 @@ enum {
>  	IO_U_F_BARRIER		= 1 << 6,
>  	IO_U_F_VER_LIST		= 1 << 7,
>  	IO_U_F_PATTERN_DONE	= 1 << 8,
> +	IO_U_F_DEVICE_ERROR	= 1 << 9,
>  };
>  
>  /*

The patches you sent should've been a series, how are they supposed to
both apply when you add an item here for each of them as if the other
one doesn't exist?

I'll fix it up, but for the future, if patches depend on each other, it
should be a series. Please check if everything works when it's pushed
out, which should be shortly.

And since I'm on a plane and this doesn't appear to want to send, when
you do see it, please also add HOWTO additions similar to the fio.1
additions you made.

-- 
Jens Axboe

  parent reply	other threads:[~2024-09-26 17:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26  0:41 [PATCH] io_uring: Add IO_U_F_DEVICE_ERROR to identify error types Minwoo Im
2024-09-26 17:33 ` Jens Axboe
2024-09-26 17:48 ` Jens Axboe [this message]
2024-09-26 18:08   ` Vincent Fu
2024-09-26 21:06     ` Jens Axboe
2024-09-26 21:17       ` Minwoo Im
2024-09-26 21:33       ` Minwoo Im
2024-09-27  0:54         ` Jens Axboe
2024-09-27  2:54           ` Minwoo Im
2024-09-26 21:13   ` Minwoo Im

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=1c383a92-ea5c-485f-9015-995c77117dfe@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=minwoo.im.dev@gmail.com \
    --cc=minwoo.im@samsung.com \
    --cc=vincent.fu@samsung.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