public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: "hch@lst•de" <hch@lst•de>
To: 전민식 <hmi.jeon@samsung•com>
Cc: "Keith Busch" <kbusch@kernel•org>,
	"Justin Tee" <justintee8345@gmail•com>,
	"axboe@kernel•dk" <axboe@kernel•dk>,
	"sven@kernel•org" <sven@kernel•org>,
	"j@jannau•net" <j@jannau•net>, "neal@gompa•dev" <neal@gompa•dev>,
	"hch@lst•de" <hch@lst•de>, "sagi@grimberg•me" <sagi@grimberg•me>,
	"justin.tee@broadcom•com" <justin.tee@broadcom•com>,
	"nareshgottumukkala83@gmail•com" <nareshgottumukkala83@gmail•com>,
	"paul.ely@broadcom•com" <paul.ely@broadcom•com>,
	"James Smart" <james.smart@broadcom•com>,
	"kch@nvidia•com" <kch@nvidia•com>,
	"linux-arm-kernel@lists•infradead.org"
	<linux-arm-kernel@lists•infradead.org>,
	"linux-nvme@lists•infradead.org" <linux-nvme@lists•infradead.org>,
	"asahi@lists•linux.dev" <asahi@lists•linux.dev>,
	"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
	이은수 <euns212.lee@samsung•com>, 칸찬 <joshi.k@samsung•com>
Subject: Re: [PATCH v4] nvme: Skip trace complete_rq on host path error
Date: Thu, 26 Mar 2026 07:14:43 +0100	[thread overview]
Message-ID: <20260326061443.GA23850@lst.de> (raw)
In-Reply-To: <20260326014429epcms2p135ffd3c2b2fface6423d045e9614c262@epcms2p1>

> -	trace_nvme_complete_rq(req);
> +	if (nvme_req(req)->status != NVME_SC_HOST_PATH_ERROR)
> +		trace_nvme_complete_rq(req);
> +

Please add a comment here explaining why we need the check.



  reply	other threads:[~2026-03-26  6:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20260320052101epcms2p42ae135da60b36685e9b7fca6849b57a6@epcms2p4>
2026-03-20  5:21 ` [PATCH] nvme: Move nvme_setup_cmd before hot_pathing 전민식
2026-03-20 13:43   ` Kanchan Joshi
2026-03-23  1:04     ` [PATCH v2] " 전민식
2026-03-22  7:16   ` [PATCH] " kernel test robot
2026-03-22  8:22   ` kernel test robot
2026-03-22 12:09   ` kernel test robot
2026-03-24 23:55   ` Justin Tee
2026-03-25  6:33     ` [PATCH v3] nvme: Add nvme_setup_cmd to host_path_error 전민식
2026-03-25 18:37       ` Justin Tee
2026-03-25 19:03         ` Keith Busch
2026-03-26  1:44           ` [PATCH v4] nvme: Skip trace complete_rq on host path error 전민식
2026-03-26  6:14             ` hch [this message]
2026-03-26  6:51               ` [PATCH v5] " 전민식
2026-03-26 14:20                 ` hch
2026-03-26 14:28                 ` Keith Busch
2026-03-26 14:31                   ` hch
2026-03-26 14:43                     ` Keith Busch
2026-03-27  6:19                       ` 전민식
2026-03-27  6:37                       ` 전민식

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=20260326061443.GA23850@lst.de \
    --to=hch@lst$(echo .)de \
    --cc=asahi@lists$(echo .)linux.dev \
    --cc=axboe@kernel$(echo .)dk \
    --cc=euns212.lee@samsung$(echo .)com \
    --cc=hmi.jeon@samsung$(echo .)com \
    --cc=j@jannau$(echo .)net \
    --cc=james.smart@broadcom$(echo .)com \
    --cc=joshi.k@samsung$(echo .)com \
    --cc=justin.tee@broadcom$(echo .)com \
    --cc=justintee8345@gmail$(echo .)com \
    --cc=kbusch@kernel$(echo .)org \
    --cc=kch@nvidia$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-nvme@lists$(echo .)infradead.org \
    --cc=nareshgottumukkala83@gmail$(echo .)com \
    --cc=neal@gompa$(echo .)dev \
    --cc=paul.ely@broadcom$(echo .)com \
    --cc=sagi@grimberg$(echo .)me \
    --cc=sven@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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