[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bc6ce1ce-3f66-4299-a922-c69d38489b7b@flourine.local>
Date: Mon, 16 Sep 2024 08:26:44 +0200
From: Daniel Wagner <dwagner@...e.de>
To: Jens Axboe <axboe@...nel.dk>
Cc: Bjorn Helgaas <helgaas@...nel.org>, Daniel Wagner <wagi@...nel.org>,
Bjorn Helgaas <bhelgaas@...gle.com>, "Michael S. Tsirkin" <mst@...hat.com>,
Jason Wang <jasowang@...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, Ming Lei <ming.lei@...hat.com>
Subject: Re: [PATCH 1/6] blk-mq: introduce blk_mq_hctx_map_queues
On Sun, Sep 15, 2024 at 02:32:30PM GMT, Jens Axboe wrote:
> > IMO this doesn't really fit well in drivers/pci since it doesn't add
> > any PCI-specific knowledge or require any PCI core internals, and the
> > parameters are blk-specific. I don't object to the code, but it seems
> > like it could go somewhere in block/?
>
> Probably not a bad idea.
Christoph suggested to move these function to matching subsystem. I am
fine either way.
> Unrelated to that topic, but Daniel, all your email gets marked as spam.
> I didn't see your series before this reply. This has been common
> recently for people that haven't kept up with kernel.org changes, please
> check for smtp changes there.
Thanks for letting me know. FWIW, I switch over to use the kernel.org smtp
server and I must miss some important config option.
Powered by blists - more mailing lists