From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Alan Adamson <alan.adamson@oracle.com>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
Hannes Reinecke <hare@suse.de>, Sagi Grimberg <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme-core: mark passthru requests RQF_QUIET flag
Date: Thu, 7 Apr 2022 19:40:35 +0000 [thread overview]
Message-ID: <f76b6953-2d1b-dd14-cf85-6bcd4648f12e@nvidia.com> (raw)
In-Reply-To: <34DD0B6B-F7F1-4BEC-B039-1B0DA9D36676@oracle.com>
On 4/6/22 16:29, Alan Adamson wrote:
> I tried the patch with my tests. It resolves the error logging with nvme/012. My verbose errors tests (nvme/039) now passes,
> but we still see the error when the system boots.
>
yes, that is something we need to fix, also it'll be great if we can
avoid top posting?
To fix this I've suggested fixing the call sites see [1].
-ck
[1]
http://lists.infradead.org/pipermail/linux-nvme/2022-April/031160.html
next prev parent reply other threads:[~2022-04-07 19:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 16:41 [PATCH] nvme-core: mark passthru requests RQF_QUIET flag Chaitanya Kulkarni
2022-04-06 16:52 ` Keith Busch
2022-04-06 17:01 ` Chaitanya Kulkarni
2022-04-06 17:21 ` Keith Busch
2022-04-06 22:06 ` Alan Adamson
2022-04-06 22:16 ` Chaitanya Kulkarni
2022-04-06 23:29 ` Alan Adamson
2022-04-07 19:40 ` Chaitanya Kulkarni [this message]
2022-04-07 8:48 ` Christoph Hellwig
2022-04-07 8:51 ` hch
2022-04-07 11:52 ` Sagi Grimberg
2022-04-07 20:10 ` Chaitanya Kulkarni
2022-04-07 20:35 ` Alan Adamson
2022-04-07 21:00 ` Chaitanya Kulkarni
2022-04-07 21:13 ` Alan Adamson
2022-04-08 2:13 ` Chaitanya Kulkarni
2022-04-08 16:24 ` Alan Adamson
2022-04-09 0:10 ` Chaitanya Kulkarni
2022-04-11 18:31 ` Alan Adamson
2022-04-11 19:53 ` Chaitanya Kulkarni
2022-04-11 21:39 ` Alan Adamson
2022-04-07 16:15 ` Alan Adamson
2022-04-06 17:03 ` 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=f76b6953-2d1b-dd14-cf85-6bcd4648f12e@nvidia.com \
--to=chaitanyak@nvidia.com \
--cc=alan.adamson@oracle.com \
--cc=hare@suse.de \
--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 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.