All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Hillf Danton <hdanton@sina.com>,
	Mohamed Khalfella <mkhalfella@purestorage.com>
Cc: Keith Busch <kbusch@kernel.org>, Ming Lei <ming.lei@redhat.com>,
	linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] nvme: Convert tag_list mutex to rwsemaphore to avoid deadlock
Date: Sun, 30 Nov 2025 19:50:33 -0700	[thread overview]
Message-ID: <c79547eb-bbc5-41cc-8fa0-fe7ec951c988@kernel.dk> (raw)
In-Reply-To: <20251201013625.9583-1-hdanton@sina.com>

Hillf, if you have nothing constructive to add, please just keep quiet.

-- 
Jens Axboe

  reply	other threads:[~2025-12-01  2:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-17 20:23 [PATCH v2 0/1] nvme: Convert tag_list mutex to rwsemaphore to avoid deadlock Mohamed Khalfella
2025-11-17 20:23 ` [PATCH v2 1/1] " Mohamed Khalfella
2025-11-18  1:34   ` Hillf Danton
2025-11-18  2:07     ` Mohamed Khalfella
2025-11-18  2:24     ` Waiman Long
2025-11-18  3:08       ` Ming Lei
2025-11-18  3:42         ` Waiman Long
2025-11-18  4:03           ` Ming Lei
     [not found]             ` <702d904c-2d9a-42b4-95b3-0fa43d91e673@redhat.com>
2025-11-18  4:50               ` Ming Lei
2025-11-18 17:59                 ` Mohamed Khalfella
2025-11-18  5:02               ` Mohamed Khalfella
2025-11-18  2:00   ` Ming Lei
2025-11-18  2:15     ` Mohamed Khalfella
2025-11-18  2:30       ` Ming Lei
2025-11-18  3:44         ` Mohamed Khalfella
2025-11-18  4:16           ` Ming Lei
2025-11-24  4:00   ` Ming Lei
2025-11-24 17:42     ` Mohamed Khalfella
2025-12-01  1:36       ` Hillf Danton
2025-12-01  2:50         ` Jens Axboe [this message]
2025-11-30 22:56   ` Sagi Grimberg

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=c79547eb-bbc5-41cc-8fa0-fe7ec951c988@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hdanton@sina.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ming.lei@redhat.com \
    --cc=mkhalfella@purestorage.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 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.