public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Kanchan Joshi <joshi.k@samsung.com>,
	hch@lst.de, kbusch@kernel.org, sagi@grimberg.me
Cc: linux-nvme@lists.infradead.org, gost.dev@samsung.com
Subject: Re: [PATCH 0/2] Granular CAP_SYS_ADMIN
Date: Tue, 25 Oct 2022 13:43:16 -0600	[thread overview]
Message-ID: <fc736207-3707-722e-c0bc-e79d111ef929@kernel.dk> (raw)
In-Reply-To: <20221020070205.57366-1-joshi.k@samsung.com>

On 10/20/22 1:02 AM, Kanchan Joshi wrote:
> Hi,
> 
> Patch 1 is for io-commands. It implements the shift to file-mode based
> policy.
> Patch 2 is to allow identify-namespace command. This is based on the feedback
> received during ALPSS.
> 
> @Sagi: Since patch 1 is changed a bit (changelog below), I did not
> apply the reviewed-by tag. Please take a look again.

I generally despise any kind of listing of commands, but this looks
pretty reasonable.

Reviewed-by: Jens Axboe <axboe@kernel.dk>

-- 
Jens Axboe




  parent reply	other threads:[~2022-10-25 19:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221020071338epcas5p16d72f5d4d868b889e3a98688bc454a98@epcas5p1.samsung.com>
2022-10-20  7:02 ` [PATCH 0/2] Granular CAP_SYS_ADMIN Kanchan Joshi
2022-10-20  7:02   ` [PATCH 1/2] nvme: fine-granular CAP_SYS_ADMIN for nvme io commands Kanchan Joshi
2022-10-20  7:02   ` [PATCH 2/2] nvme: identify-namespace without CAP_SYS_ADMIN Kanchan Joshi
2022-10-31  6:55     ` Chaitanya Kulkarni
2022-10-31 13:47       ` Kanchan Joshi
2022-11-01  5:20         ` Chaitanya Kulkarni
2022-10-25 19:43   ` Jens Axboe [this message]
2022-10-25 20:07   ` [PATCH 0/2] Granular CAP_SYS_ADMIN Keith Busch

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=fc736207-3707-722e-c0bc-e79d111ef929@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=gost.dev@samsung.com \
    --cc=hch@lst.de \
    --cc=joshi.k@samsung.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox