All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Seungcheol Lee <sc108.lee@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: axboe@fb.com, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme.h: expend lbaf on nvme_id_ns, lbafe on nvme_zns_id_ns
Date: Tue, 28 Sep 2021 17:45:08 +0900	[thread overview]
Message-ID: <CAGrZSEwg4Nh+4CTSA024iGOS435zb1FywAtvefyAq4B0CecpZA@mail.gmail.com> (raw)
In-Reply-To: <CAGrZSExsxVcPaqpo-bh+Bekb+dxvQf8rNFMXxX7-9_+f7DYECQ@mail.gmail.com>

Sorry guys misunderstood, I just realized that changes need other
functionality that you guys mention.
Thanks for the chekcing :)
Just ignore this patch ~

2021년 9월 28일 (화) 오후 12:44, Steven Seungcheol Lee <sc108.lee@gmail.com>님이 작성:
>
> That means leave other elements and fix lbf only?
>
> The changes for lbaf, lbafe happens.
> so I thought same structure should be updated as same version of spec.
>
> If not recommanded, I wll change as below.
>
> id_ns
> mssrl, mcl, msrc => remove
> rsvd area -> lbaf[64]
>
> id_zns
> rrl1~3, frl1~3 => remove
> rsvd area -> lbafe[64]

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

      reply	other threads:[~2021-09-28  8:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-26  4:34 [PATCH] nvme.h: expend lbaf on nvme_id_ns, lbafe on nvme_zns_id_ns Steven Seungcheol Lee
2021-09-27 10:24 ` Niklas Cassel
2021-09-27 19:23 ` Chaitanya Kulkarni
2021-09-27 20:03 ` Keith Busch
2021-09-28  2:19   ` Steven Seungcheol Lee
2021-09-28  2:43     ` Keith Busch
2021-09-28  2:51       ` Steven Seungcheol Lee
2021-09-28  2:59         ` Keith Busch
2021-09-28  3:44           ` Steven Seungcheol Lee
2021-09-28  8:45             ` Steven Seungcheol Lee [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=CAGrZSEwg4Nh+4CTSA024iGOS435zb1FywAtvefyAq4B0CecpZA@mail.gmail.com \
    --to=sc108.lee@gmail.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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.