From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Daniel Wagner <dwagner@suse.de>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Hannes Reinecke <hare@suse.de>, Sagi Grimberg <sagi@grimberg.me>,
Jason Gunthorpe <jgg@ziepe.ca>,
Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH blktests v4 0/3] Introduce nvmet target setup/cleanup helpers
Date: Thu, 31 Aug 2023 08:03:47 +0000 [thread overview]
Message-ID: <f0e73932-1ef5-1792-383f-7e516a7b8446@nvidia.com> (raw)
In-Reply-To: <yhnyazgqmgbzsa5irt4cu3735qxuvbl5czicsaxl7zm6ckjkzf@2cs7fpg2qvpb>
>> [1] https://lore.kernel.org/linux-nvme/5h333eqhtw252sjw6axjewlb5bbb5ze7awekczxe3kie2lnhw6@manyer42khct/
>
> I've applied the series with the fix noted for the 3rd patch. I also reverted
> the commit 26664dff17b6 together. Thanks again for this clean up :)
Seriously thanks again, it was due long time ago.
-ck
prev parent reply other threads:[~2023-08-31 8:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 9:20 [PATCH blktests v4 0/3] Introduce nvmet target setup/cleanup helpers Daniel Wagner
2023-08-30 9:20 ` [PATCH blktests v4 1/3] nvme/{033,034,035,036}: use default subsysnqn variable directly Daniel Wagner
2023-08-30 9:20 ` [PATCH blktests v4 2/3] nvme/{033,034,035,036,37}: drop port handle between passthru target setup and cleanup Daniel Wagner
2023-08-30 9:20 ` [PATCH blktests v4 3/3] nvme: introduce nvmet_target_{setup/cleanup} common code Daniel Wagner
2023-08-30 13:38 ` Shinichiro Kawasaki
2023-08-30 15:06 ` Daniel Wagner
2023-08-31 2:25 ` [PATCH blktests v4 0/3] Introduce nvmet target setup/cleanup helpers Shinichiro Kawasaki
2023-08-31 8:03 ` Chaitanya Kulkarni [this message]
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=f0e73932-1ef5-1792-383f-7e516a7b8446@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=bvanassche@acm.org \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=jgg@ziepe.ca \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.com \
/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