[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220629054027.GB16297@lst.de>
Date: Wed, 29 Jun 2022 07:40:27 +0200
From: Christoph Hellwig <hch@....de>
To: John Garry <john.garry@...wei.com>
Cc: Damien Le Moal <damien.lemoal@...nsource.wdc.com>, hch@....de,
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 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.
Powered by blists - more mailing lists