From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: "alan.adamson@oracle.com" <alan.adamson@oracle.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Christoph Hellwig <hch@lst.de>,
"kbusch@kernel.org" <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: [PATCH V5 0/1] nvme: allow passthru cmd error logging
Date: Fri, 5 May 2023 23:56:01 +0000 [thread overview]
Message-ID: <6835206b-e28c-8ad8-b468-32b7d7208535@nvidia.com> (raw)
In-Reply-To: <c9ed84c9-58fd-37d1-138c-869726ccc7d6@oracle.com>
On 5/5/23 14:59, alan.adamson@oracle.com wrote:
>
>>>>> In nvme_end_req()_ we only log errors which are for non-passthru
>>>>> commands. Add a helper function nvme_log_err_passthru() which
>>>>> allows us
>>>>> to log error for passthru commands by decoding cdw10-cdw15 values of
>>>>> nvme command.
>>>> CK,
>>>>
>>>> Thanks for doing this. Looks good. I've tested it in my environment.
>>>>
>>>> Alan
>>>>
>>>>
>>> Thanks for having a look, let's wait for others to have comments.
>>>
>>> -ck
>>
>> I'll be on vacation next week so we will move forward with the patch
>> when I get back on 4/24.
>
> I'm back from vacation. We can continue with the review.
>
>
> Thanks,
>
> Alan
>
since you've tested V5 in your environment, I think we can pick this up
before
next PR if there is no major objection ...
-ck
next prev parent reply other threads:[~2023-05-05 23:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230412091843eucas1p22a4c7c34297c4f260ccc54cff9d67a52@eucas1p2.samsung.com>
2023-04-09 21:25 ` [PATCH V5 0/1] nvme: allow passthru cmd error logging Chaitanya Kulkarni
2023-04-09 21:25 ` [PATCH V5 1/1] " Chaitanya Kulkarni
2023-05-22 22:58 ` alan.adamson
2023-05-23 0:08 ` Chaitanya Kulkarni
2023-06-15 16:48 ` alan.adamson
2023-04-11 0:05 ` [PATCH V5 0/1] " alan.adamson
2023-04-11 5:23 ` Chaitanya Kulkarni
2023-04-14 22:01 ` alan.adamson
2023-05-05 21:59 ` alan.adamson
2023-05-05 23:56 ` Chaitanya Kulkarni [this message]
2023-05-13 10:13 ` Chaitanya Kulkarni
2023-04-12 9:10 ` Pankaj Raghav
2023-04-13 2:20 ` 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=6835206b-e28c-8ad8-b468-32b7d7208535@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=alan.adamson@oracle.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