From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "hch@lst.de" <hch@lst.de>, "sagi@grimberg.me" <sagi@grimberg.me>,
"kbusch@kernel.org" <kbusch@kernel.org>
Subject: Re: [PATCH 0/3] nvme: fix internal passthru error messages
Date: Mon, 11 Apr 2022 03:14:20 +0000 [thread overview]
Message-ID: <100b676f-8da0-bc2a-ce74-2d30490dacb2@nvidia.com> (raw)
In-Reply-To: <20220411031235.5085-1-kch@nvidia.com>
On 4/10/22 20:12, Chaitanya Kulkarni wrote:
> Hi,
>
> Since addition of the nvme_log_error(), we are getting reports of
> the error messages are printed from internal passthru commands.
> This also uncovered target execute identify code path where we don't
> handle the case for NVME_CSI_NVM and in the host where we issue
> non-mdts limit for the discovery contoller.
Please ignore this ..
-ck
next prev parent reply other threads:[~2022-04-11 3:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 3:12 [PATCH 0/3] nvme: fix internal passthru error messages Chaitanya Kulkarni
2022-04-11 3:14 ` Chaitanya Kulkarni [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-04-11 3:12 Chaitanya Kulkarni
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=100b676f-8da0-bc2a-ce74-2d30490dacb2@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=hch@lst.de \
--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