From: Hannes Reinecke <hare@suse.de>
To: John Garry <john.g.garry@oracle.com>,
axboe@kernel.dk, martin.petersen@oracle.com,
James.Bottomley@HansenPartnership.com, hch@lst.de
Cc: linux-block@vger.kernel.org, linux-scsi@vger.kernel.org,
himanshu.madhani@oracle.com
Subject: Re: [PATCH 1/2] scsi: core: Pass sdev to blk_mq_alloc_queue()
Date: Tue, 11 Jun 2024 08:21:01 +0200 [thread overview]
Message-ID: <7913e2c2-e348-49bc-ad76-dffc4dc2acf7@suse.de> (raw)
In-Reply-To: <20240524084829.2132555-2-john.g.garry@oracle.com>
On 5/24/24 10:48, John Garry wrote:
> When calling scsi_alloc_sdev() -> blk_mq_alloc_queue(), we don't pass
> the sdev as the queuedata, but rather manually set it afterwards. Just
> pass to blk_mq_alloc_queue() to have automatically set.
>
> Signed-off-by: John Garry <john.g.garry@oracle.com>
> ---
> drivers/scsi/scsi_scan.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2024-06-11 6:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 8:48 [PATCH 0/2] block, scsi: Small improvements for blk_mq_alloc_queue() usage John Garry
2024-05-24 8:48 ` [PATCH 1/2] scsi: core: Pass sdev to blk_mq_alloc_queue() John Garry
2024-05-24 9:38 ` Christoph Hellwig
2024-05-24 10:26 ` Hannes Reinecke
2024-06-11 6:21 ` Hannes Reinecke [this message]
2024-05-24 8:48 ` [PATCH 2/2] scsi: bsg: Pass dev " John Garry
2024-05-24 9:38 ` Christoph Hellwig
2024-05-24 10:26 ` Hannes Reinecke
2024-05-29 20:30 ` [PATCH 0/2] block, scsi: Small improvements for blk_mq_alloc_queue() usage Himanshu Madhani
2024-05-31 0:23 ` Martin K. Petersen
2024-06-05 2:32 ` 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=7913e2c2-e348-49bc-ad76-dffc4dc2acf7@suse.de \
--to=hare@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=himanshu.madhani@oracle.com \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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