All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>,
	Andreas Hindborg <a.hindborg@samsung.com>
Subject: Re: [PATCH V2] ublk: zoned: support REQ_OP_ZONE_RESET_ALL
Date: Thu, 10 Aug 2023 15:09:51 +0000	[thread overview]
Message-ID: <ZNT9ua6noDjP+CI6@x1-carbon> (raw)
In-Reply-To: <ZNT4cjB7bh4jDaNl@fedora>

On Thu, Aug 10, 2023 at 10:47:14PM +0800, Ming Lei wrote:
> On Thu, Aug 10, 2023 at 02:22:50PM +0000, Niklas Cassel wrote:
> > On Thu, Aug 10, 2023 at 10:00:14PM +0800, Ming Lei wrote:
> > > On Thu, Aug 10, 2023 at 01:10:30PM +0000, Niklas Cassel wrote:
> > > > On Thu, Aug 10, 2023 at 08:43:26PM +0800, Ming Lei wrote:
> 
> We have 256 OP available, which is big enough for future extend, and OP
> code can be used from any offset, but still more readable to group them
> according to their category. And it isn't big deal to use which number
> for which command, what matters is that we can extend, and keep
> compatible.

I see your point, cheers!


Kind regards,
Niklas

  reply	other threads:[~2023-08-10 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 12:43 [PATCH V2] ublk: zoned: support REQ_OP_ZONE_RESET_ALL Ming Lei
2023-08-10 13:10 ` Niklas Cassel
2023-08-10 14:00   ` Ming Lei
2023-08-10 14:22     ` Niklas Cassel
2023-08-10 14:47       ` Ming Lei
2023-08-10 15:09         ` Niklas Cassel [this message]
2023-08-14  2:01 ` Ming Lei
2023-08-21  2:16   ` Ming Lei
2023-08-21  2:25 ` Jens Axboe

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=ZNT9ua6noDjP+CI6@x1-carbon \
    --to=niklas.cassel@wdc.com \
    --cc=a.hindborg@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=ming.lei@redhat.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 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.