[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241113143039.GA20331@lst.de>
Date: Wed, 13 Nov 2024 15:30:39 +0100
From: Christoph Hellwig <hch@....de>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: John Garry <john.g.garry@...cle.com>, Daniel Wagner <dwagner@...e.de>,
Daniel Wagner <wagi@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Bjorn Helgaas <bhelgaas@...gle.com>,
"Michael S. Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...hat.com>,
Xuan Zhuo <xuanzhuo@...ux.alibaba.com>,
Eugenio PĂ©rez <eperezma@...hat.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Keith Busch <kbusch@...nel.org>, Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org,
virtualization@...ts.linux.dev, linux-scsi@...r.kernel.org,
megaraidlinux.pdl@...adcom.com, mpi3mr-linuxdrv.pdl@...adcom.com,
MPT-FusionLinux.pdl@...adcom.com, storagedev@...rochip.com,
linux-nvme@...ts.infradead.org
Subject: Re: [PATCH v3 1/8] driver core: bus: add irq_get_affinity callback
to bus_type
On Wed, Nov 13, 2024 at 02:54:23PM +0100, Greg Kroah-Hartman wrote:
> bus types are good to set it at a bus level so you don't have to
> explicitly set it at each-and-every-driver. Depends on what you want
> this to be, if it is a "all drivers of this bus type will have the same
> callback" then put it on the bus. otherwise if you are going to
> mix/match on a same bus, then put it in the driver structure.
... and that is exactly the case here. The driver itself has no business
being involved.
Powered by blists - more mailing lists