linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Ming Lei <ming.lei@redhat.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org,
	Sebastian Reichel <sebastian.reichel@collabora.com>,
	Jens Axboe <axboe@kernel.dk>,
	"James E.J. Bottomley" <James.Bottomley@hansenpartnership.com>
Subject: Re: [PATCH] scsi: core: Fix a regression triggered by scsi_host_busy()
Date: Tue, 7 Oct 2025 22:50:10 -0700	[thread overview]
Message-ID: <aOX7krhcR7DB7T6a@infradead.org> (raw)
In-Reply-To: <CAFj5m9K1L7n3C9mL0zgNXmzhttD-B-64LBNbcp=HCPYPNvgjMg@mail.gmail.com>

On Wed, Oct 08, 2025 at 11:17:18AM +0800, Ming Lei wrote:
> Long term, the UFS driver need to be fixed, this or most of scsi core
> APIs should
> have been called after the scsi host is initialized.

Please fix ufs now.  Otherwise we'll be stuck with these hacks forever
as they never get cleaned up.


  reply	other threads:[~2025-10-08  5:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07 21:48 [PATCH] scsi: core: Fix a regression triggered by scsi_host_busy() Bart Van Assche
2025-10-08  3:17 ` Ming Lei
2025-10-08  5:50   ` Christoph Hellwig [this message]
2025-10-08 12:49     ` Sebastian Reichel
2025-10-08 15:48       ` Bart Van Assche
2025-10-08 15:42     ` Bart Van Assche
2025-10-08  7:03 ` John Garry
2025-10-08 17:53   ` Bart Van Assche
2025-10-08 12:33 ` Sebastian Reichel
2025-10-22  2:26 ` Martin K. Petersen
2025-10-22  8:13   ` John Garry
2025-10-22 18:07     ` Bart Van Assche
2025-10-23  8:31       ` John Garry
2025-10-23 16:32         ` Bart Van Assche

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=aOX7krhcR7DB7T6a@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.com \
    --cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).