From: Christoph Hellwig <hch@lst.de>
To: Sagi Grimberg <sagi@grimberg.me>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Keith Busch <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Christoph Hellwig <hch@lst.de>,
Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
Subject: Re: [PATCH 0/7] nvme: cleanup ida_simple_[get|remove]
Date: Tue, 15 Feb 2022 19:42:21 +0100 [thread overview]
Message-ID: <20220215184221.GA24543@lst.de> (raw)
In-Reply-To: <705ce6ee-3c1a-c4a0-1662-2f0794b1a6fe@grimberg.me>
On Mon, Feb 14, 2022 at 12:59:49PM +0200, Sagi Grimberg wrote:
>> I did cc you, here is the link, somehow it takes a while to appear
>> on the mailing list than it appears in my mail box :-
>
> Yea, got it, just a tad late...
So which of the two versions should we go with? Either one will need
reviews :)
next prev parent reply other threads:[~2022-02-15 18:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 9:07 [PATCH 0/7] nvme: cleanup ida_simple_[get|remove] Sagi Grimberg
2022-02-14 9:07 ` [PATCH 1/7] nvme-tcp: fix bogus request completion when failing to send AER Sagi Grimberg
2022-02-14 10:52 ` Chaitanya Kulkarni
2022-02-14 10:59 ` Sagi Grimberg
2022-02-14 9:07 ` [PATCH 2/7] nvme: replace ida_simple[get|remove] with the simler ida_[alloc|free] Sagi Grimberg
2022-02-14 9:07 ` [PATCH 3/7] nvme-fc: " Sagi Grimberg
2022-02-14 9:07 ` [PATCH 4/7] nvmet: " Sagi Grimberg
2022-02-14 9:07 ` [PATCH 5/7] nvmet-fc: " Sagi Grimberg
2022-02-14 9:07 ` [PATCH 6/7] nvmet-rdma: " Sagi Grimberg
2022-02-14 9:07 ` [PATCH 7/7] nvmet-tcp: " Sagi Grimberg
2022-02-14 10:03 ` [PATCH 0/7] nvme: cleanup ida_simple_[get|remove] Chaitanya Kulkarni
2022-02-14 10:22 ` Sagi Grimberg
2022-02-14 10:44 ` Chaitanya Kulkarni
2022-02-14 10:59 ` Sagi Grimberg
2022-02-15 18:42 ` Christoph Hellwig [this message]
2022-02-15 19:15 ` Chaitanya Kulkarni
2022-02-15 19:27 ` Keith Busch
2022-02-15 20:01 ` Chaitanya Kulkarni
2022-02-16 8:02 ` Christoph Hellwig
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=20220215184221.GA24543@lst.de \
--to=hch@lst.de \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=chaitanyak@nvidia.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