[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <65e05dd1-8e92-5f6b-d68e-72987fcebf59@huawei.com>
Date: Wed, 29 Jun 2022 08:43:30 +0100
From: John Garry <john.garry@...wei.com>
To: Damien Le Moal <damien.lemoal@...nsource.wdc.com>,
Christoph Hellwig <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 29/06/2022 06:58, Damien Le Moal wrote:
> On 6/29/22 14:40, Christoph Hellwig wrote:
>> On Tue, Jun 28, 2022 at 12:33:58PM +0100, John Garry wrote:
>>> 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?
>>
>> The offer still stands, and I don't really care where the libata
>> patch is routed. Just tell me what you prefer.
Cheers.
>
> If it is 100% independent from the other patches, I can take it.
> Otherwise, feel free to take it !
>
I'll just keep the all together - it's easier in case I need to change
anything.
Thanks!
Powered by blists - more mailing lists