Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Maurizio Lombardi <mlombard@redhat.com>
Cc: kbusch@kernel.org, mheyne@amazon.de, emilne@redhat.com,
	jmeneghi@redhat.com, linux-nvme@lists.infradead.org,
	dwagner@suse.de, mlombard@arkamax.eu, mkhalfella@purestorage.com,
	chaitanyak@nvidia.com, hare@kernel.org, hch@lst.de
Subject: Re: [PATCH V3 4/8] nvme: add sysfs attribute to change IO timeout per nvme controller
Date: Fri, 24 Apr 2026 15:40:16 +0200	[thread overview]
Message-ID: <20260424134016.GB16434@lst.de> (raw)
In-Reply-To: <20260410073924.61078-5-mlombard@redhat.com>

nit: the second nvme in the subject is redundant.



  reply	other threads:[~2026-04-24 13:40 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-10  7:39 [PATCH V3 0/8] nvme: Refactor and expose per-controller timeout configuration Maurizio Lombardi
2026-04-10  7:39 ` [PATCH V3 1/8] nvme: Let the blocklayer set timeouts for requests Maurizio Lombardi
2026-04-22  9:58   ` Daniel Wagner
2026-04-24 13:38   ` Christoph Hellwig
2026-04-10  7:39 ` [PATCH V3 2/8] nvme: add sysfs attribute to change admin timeout per nvme controller Maurizio Lombardi
2026-04-22 10:10   ` Daniel Wagner
2026-04-22 11:08     ` Maurizio Lombardi
2026-04-23 12:46       ` Daniel Wagner
2026-04-23 12:58         ` Maurizio Lombardi
2026-04-23 17:04           ` Daniel Wagner
2026-04-23 18:35             ` Maurizio Lombardi
2026-04-23 13:45         ` Hannes Reinecke
2026-04-10  7:39 ` [PATCH V3 3/8] nvme: pci: use admin queue timeout over NVME_ADMIN_TIMEOUT Maurizio Lombardi
2026-04-27  9:05   ` Daniel Wagner
2026-04-10  7:39 ` [PATCH V3 4/8] nvme: add sysfs attribute to change IO timeout per nvme controller Maurizio Lombardi
2026-04-24 13:40   ` Christoph Hellwig [this message]
2026-04-27  9:11   ` Daniel Wagner
2026-04-27  9:13     ` Maurizio Lombardi
2026-04-27  9:19       ` Daniel Wagner
2026-04-28 17:23   ` Mohamed Khalfella
2026-04-29 12:06     ` Maurizio Lombardi
2026-04-10  7:39 ` [PATCH V3 5/8] nvme: use per controller timeout waits over depending on global default Maurizio Lombardi
2026-04-27  9:22   ` Daniel Wagner
2026-04-10  7:39 ` [PATCH V3 6/8] nvme-core: align fabrics_q teardown with admin_q in nvme_free_ctrl Maurizio Lombardi
2026-04-27  9:35   ` Daniel Wagner
2026-04-10  7:39 ` [PATCH V3 7/8] nvmet-loop: do not alloc admin tag set during reset Maurizio Lombardi
2026-04-27  9:46   ` Daniel Wagner
2026-04-27  9:47     ` Maurizio Lombardi
2026-04-28 11:17     ` Maurizio Lombardi
2026-04-28 12:46       ` Daniel Wagner
2026-05-07 16:23       ` Daniel Wagner
2026-05-08  6:14         ` Maurizio Lombardi
2026-04-10  7:39 ` [PATCH V3 8/8] nvme-core: warn on allocating admin tag set with existing queue Maurizio Lombardi
2026-04-24 13:40   ` Christoph Hellwig
2026-04-27  9:54   ` Daniel Wagner
2026-04-13  8:12 ` [PATCH V3 0/8] nvme: Refactor and expose per-controller timeout configuration Hannes Reinecke
2026-04-13  9:21   ` Maurizio Lombardi
2026-04-14 19:14     ` John Meneghini

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=20260424134016.GB16434@lst.de \
    --to=hch@lst.de \
    --cc=chaitanyak@nvidia.com \
    --cc=dwagner@suse.de \
    --cc=emilne@redhat.com \
    --cc=hare@kernel.org \
    --cc=jmeneghi@redhat.com \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=mheyne@amazon.de \
    --cc=mkhalfella@purestorage.com \
    --cc=mlombard@arkamax.eu \
    --cc=mlombard@redhat.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