From: Minwoo Im <minwoo.im.dev@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-nvme@lists.infradead.org, "Keith Busch" <kbusch@kernel.org>,
"Jens Axboe" <axboe@fb.com>, "Sagi Grimberg" <sagi@grimberg.me>,
"Kanchan Joshi" <joshiiitr@gmail.com>,
"Javier González" <javier.gonz@samsung.com>
Subject: Re: [PATCH V2 1/1] nvme: introduce generic per-namespace chardev
Date: Thu, 8 Apr 2021 01:59:50 +0900 [thread overview]
Message-ID: <20210407165950.GA9994@localhost> (raw)
In-Reply-To: <20210407164818.GA31878@lst.de>
On 21-04-07 18:48:18, Christoph Hellwig wrote:
> I've force pushed the branch with the updates, let me know if this
> looks good to you.
Checked the commit. IS_ENABLED() makes code much more cleaner by
removing the #ifdef from the .c file. Also checked that the
mutex_unlock in nvme_find_get_live_ctrl().
Otherwise, the generic ns patch commit description looks like needs to
be updated: it's still saying that nvme-generic-XnY, and also about the
module parameter that's been removed in this series.
Tested again based on the force pushed branch.
Thanks!
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-04-07 17:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 6:48 [PATCH V2 0/1] nvme: introduce generic per-namespace chardev Minwoo Im
2021-04-06 6:48 ` [PATCH V2 1/1] " Minwoo Im
2021-04-07 13:15 ` Christoph Hellwig
2021-04-07 14:11 ` Minwoo Im
2021-04-07 14:21 ` Christoph Hellwig
2021-04-07 15:35 ` Minwoo Im
2021-04-07 15:40 ` Christoph Hellwig
2021-04-07 15:44 ` Minwoo Im
2021-04-07 15:47 ` Minwoo Im
2021-04-07 16:48 ` Christoph Hellwig
2021-04-07 16:59 ` Minwoo Im [this message]
2021-04-07 17:09 ` Minwoo Im
2021-04-07 17:14 ` Christoph Hellwig
2021-04-08 7:11 ` Javier González
2021-04-08 7:26 ` Christoph Hellwig
2021-04-08 10:26 ` Javier González
2021-04-08 11:27 ` Christoph Hellwig
2021-04-08 11:46 ` Javier González
2021-04-08 12:41 ` Minwoo Im
2021-04-06 9:01 ` [PATCH V2 0/1] " Niklas Cassel
2021-04-06 13:35 ` Minwoo Im
2021-04-06 14:59 ` Christoph Hellwig
2021-04-06 16:23 ` Minwoo Im
2021-04-07 6:00 ` Christoph Hellwig
2021-04-07 6:02 ` Minwoo Im
2021-04-07 7:36 ` Niklas Cassel
2021-04-07 9:39 ` Christoph Hellwig
2021-04-07 10:00 ` Niklas Cassel
2021-04-07 10:34 ` Damien Le Moal
2021-04-07 11:50 ` Javier González
2021-04-06 14:13 ` Kanchan Joshi
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=20210407165950.GA9994@localhost \
--to=minwoo.im.dev@gmail.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=javier.gonz@samsung.com \
--cc=joshiiitr@gmail.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 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.