From: "Javier González" <javier@javigon.com>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-block@vger.kernel.org, minwoo.im.dev@gmail.com, hch@lst.de,
linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: nvme: enable char device per namespace
Date: Thu, 17 Dec 2020 14:29:36 +0100 [thread overview]
Message-ID: <20201217132936.3wvuguclzwll5kqu@unifi> (raw)
In-Reply-To: <20201216175311.GA31311@redsun51.ssa.fujisawa.hgst.com>
On 17.12.2020 02:53, Keith Busch wrote:
>On Wed, Dec 16, 2020 at 06:43:22PM +0100, Javier González wrote:
>> Thanks Keith. I will send a new version today.
>>
>> Regarding nvme-cli: what are your thoughts?
>
>I was thinking we could add a column for these with the '--verbose'
>option in the namespace section.
Makes sense. I will look into it - probably on the other side of
Christmas. Should give plenty of time since this till not be merged
until 5.12.
Should give me time to add multipath in a follow-up patch then.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2020-12-17 13:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 19:55 [PATCH V3] nvme: enable char device per namespace javier
2020-12-15 22:12 ` Keith Busch
2020-12-16 8:01 ` Javier González
2020-12-15 22:46 ` Keith Busch
2020-12-16 8:01 ` Javier González
2020-12-16 16:26 ` Keith Busch
2020-12-16 17:43 ` Javier González
2020-12-16 17:53 ` Keith Busch
2020-12-17 13:29 ` Javier González [this message]
[not found] <CGME20201216181838eucas1p15c687e5d1319d3fa581990e6cca73295@eucas1p1.samsung.com>
2020-12-16 18:18 ` [PATCH V4] " javier
2021-01-11 18:53 ` Javier González
2021-01-12 9:22 ` Minwoo Im
2021-01-12 11:26 ` Minwoo Im
2021-01-12 18:30 ` Javier González
2021-01-12 18:33 ` Christoph Hellwig
2021-01-12 18:41 ` Javier González
-- strict thread matches above, loose matches on Subject: below --
2020-12-08 13:29 [PATCH V2] " javier
2020-12-08 14:21 ` Christoph Hellwig
2020-12-09 9:16 ` Javier González
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=20201217132936.3wvuguclzwll5kqu@unifi \
--to=javier@javigon.com \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=minwoo.im.dev@gmail.com \
--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