From: Christoph Hellwig <hch@lst.de>
To: "Javier González" <javier@javigon.com>
Cc: Minwoo Im <minwoo.im.dev@gmail.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
hch@lst.de, kbusch@kernel.org, sagi@grimberg.me
Subject: Re: nvme: enable char device per namespace
Date: Tue, 12 Jan 2021 19:33:03 +0100 [thread overview]
Message-ID: <20210112183303.GA5050@lst.de> (raw)
In-Reply-To: <20210112183055.u3y34tfxh4d5aeue@unifi>
On Tue, Jan 12, 2021 at 07:30:55PM +0100, Javier González wrote:
> I have not implemented multipath support, but it should definitely not
> crash like this. I'll rebase to 5.11 and test.
>
> Christoph: Is it OK to send this without multipath or should I just send
> all together?
We're not in a rush at the moment, so I'd prefer working multipath
support if you can spare a few cycles.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: "Javier González" <javier@javigon.com>
Cc: sagi@grimberg.me, linux-nvme@lists.infradead.org,
linux-block@vger.kernel.org, Minwoo Im <minwoo.im.dev@gmail.com>,
kbusch@kernel.org, hch@lst.de
Subject: Re: nvme: enable char device per namespace
Date: Tue, 12 Jan 2021 19:33:03 +0100 [thread overview]
Message-ID: <20210112183303.GA5050@lst.de> (raw)
In-Reply-To: <20210112183055.u3y34tfxh4d5aeue@unifi>
On Tue, Jan 12, 2021 at 07:30:55PM +0100, Javier González wrote:
> I have not implemented multipath support, but it should definitely not
> crash like this. I'll rebase to 5.11 and test.
>
> Christoph: Is it OK to send this without multipath or should I just send
> all together?
We're not in a rush at the moment, so I'd prefer working multipath
support if you can spare a few cycles.
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-01-12 18:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201216181838eucas1p15c687e5d1319d3fa581990e6cca73295@eucas1p1.samsung.com>
2020-12-16 18:18 ` [PATCH V4] nvme: enable char device per namespace javier
2020-12-16 18:18 ` javier
2021-01-11 18:53 ` Javier González
2021-01-11 18:53 ` Javier González
2021-01-12 9:22 ` Minwoo Im
2021-01-12 9:22 ` Minwoo Im
2021-01-12 11:26 ` Minwoo Im
2021-01-12 11:26 ` Minwoo Im
2021-01-12 18:30 ` Javier González
2021-01-12 18:30 ` Javier González
2021-01-12 18:33 ` Christoph Hellwig [this message]
2021-01-12 18:33 ` Christoph Hellwig
2021-01-12 18:41 ` Javier González
2021-01-12 18:41 ` Javier González
2020-12-15 22:46 [PATCH V3] " 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:43 ` Javier González
2020-12-16 17:53 ` Keith Busch
2020-12-16 17:53 ` Keith Busch
2020-12-17 13:29 ` Javier González
2020-12-17 13:29 ` 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
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=20210112183303.GA5050@lst.de \
--to=hch@lst.de \
--cc=javier@javigon.com \
--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 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.