[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1f523333-1de5-2a09-0476-298edcbba413@huawei.com>
Date: Tue, 19 Jul 2022 10:10:22 +0100
From: John Garry <john.garry@...wei.com>
To: Christoph Hellwig <hch@....de>
CC: Damien Le Moal <damien.lemoal@...nsource.wdc.com>,
<joro@...tes.org>, <will@...nel.org>, <jejb@...ux.ibm.com>,
<martin.petersen@...cle.com>, <m.szyprowski@...sung.com>,
<robin.murphy@....com>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-ide@...r.kernel.org>,
<iommu@...ts.linux.dev>, <linux-scsi@...r.kernel.org>,
<linuxarm@...wei.com>
Subject: Re: [PATCH v6 4/6] scsi: sd: Allow max_sectors be capped at DMA
optimal size limit
On 19/07/2022 08:10, Christoph Hellwig wrote:
> On Tue, Jul 19, 2022 at 08:05:30AM +0100, John Garry wrote:
>> Christoph has now applied this (thanks, BTW), so would you like me to
>> follow up with a patch on top with a comment?
> Please do.
ok, fine, I'll do it now.
Just saying in case it's an issue - I was looking at
http://git.infradead.org/users/hch/dma-mapping.git/log/refs/heads/for-next
and the order is not the same as this series and would cause an
intermediate build breakage at 9f5ec52ae501 ("scsi: scsi_transport_sas:
cap shost opt_sectors according to DMA optimal limit")
Cheers,
John
Powered by blists - more mailing lists