[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <38ae1cc8-1411-bb54-e082-0f7b91cb9e63@huawei.com>
Date: Tue, 28 Jun 2022 12:33:58 +0100
From: John Garry <john.garry@...wei.com>
To: Damien Le Moal <damien.lemoal@...nsource.wdc.com>, <hch@....de>
CC: <linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-ide@...r.kernel.org>, <iommu@...ts.linux-foundation.org>,
<iommu@...ts.linux.dev>, <linux-scsi@...r.kernel.org>,
<linuxarm@...wei.com>, <joro@...tes.org>, <will@...nel.org>,
<jejb@...ux.ibm.com>, <martin.petersen@...cle.com>,
<m.szyprowski@...sung.com>, <robin.murphy@....com>
Subject: Re: [PATCH v4 5/5] libata-scsi: Cap ata_device->max_sectors according
to shost->max_sectors
On 28/06/2022 10:14, Damien Le Moal wrote:
>> BTW, this patch has no real dependency on the rest of the series, so
>> could be taken separately if you prefer.
> Sure, you can send it separately. Adding it through the scsi tree is fine too.
>
Well Christoph originally offered to take this series via the
dma-mapping tree.
@Christoph, is that still ok with you? If so, would you rather I send
this libata patch separately?
Thanks,
john
Powered by blists - more mailing lists