public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: martin.petersen@oracle.com, haowenchao@huawei.com,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH] sd: don't call blk_cleanup_disk in sd_probe
Date: Mon, 23 May 2022 23:16:39 -0400	[thread overview]
Message-ID: <yq1ilpvhb73.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20220523083813.227935-1-hch@lst.de> (Christoph Hellwig's message of "Mon, 23 May 2022 10:38:13 +0200")


Christoph,

> In SCSI the midlayer has ownership of the request_queue, so on probe
> failure we must only put the gendisk, but leave the request_queue alone.

Applied to 5.19/scsi-staging, thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  reply	other threads:[~2022-05-24  3:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23  8:38 [PATCH] sd: don't call blk_cleanup_disk in sd_probe Christoph Hellwig
2022-05-24  3:16 ` Martin K. Petersen [this message]
2022-05-24 18:11 ` Martin K. Petersen

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=yq1ilpvhb73.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=haowenchao@huawei.com \
    --cc=hch@lst.de \
    --cc=linux-scsi@vger.kernel.org \
    /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