From: Damien Le Moal via iommu <iommu@lists.linux-foundation.org>
To: John Garry <john.garry@huawei.com>, Christoph Hellwig <hch@lst.de>
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
linux-doc@vger.kernel.org, robin.murphy@arm.com,
linuxarm@huawei.com, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
iommu@lists.linux-foundation.org, will@kernel.org,
jejb@linux.ibm.com
Subject: Re: [PATCH v4 5/5] libata-scsi: Cap ata_device->max_sectors according to shost->max_sectors
Date: Wed, 29 Jun 2022 17:24:41 +0900 [thread overview]
Message-ID: <bf9d1cc7-c03d-f5a8-bb96-cfcd352ac36e@opensource.wdc.com> (raw)
In-Reply-To: <65e05dd1-8e92-5f6b-d68e-72987fcebf59@huawei.com>
On 6/29/22 16:43, John Garry wrote:
> 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.
Works for me.
>
> Thanks!
--
Damien Le Moal
Western Digital Research
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: John Garry <john.garry@huawei.com>, Christoph Hellwig <hch@lst.de>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org, iommu@lists.linux-foundation.org,
iommu@lists.linux.dev, linux-scsi@vger.kernel.org,
linuxarm@huawei.com, joro@8bytes.org, will@kernel.org,
jejb@linux.ibm.com, martin.petersen@oracle.com,
m.szyprowski@samsung.com, robin.murphy@arm.com
Subject: Re: [PATCH v4 5/5] libata-scsi: Cap ata_device->max_sectors according to shost->max_sectors
Date: Wed, 29 Jun 2022 17:24:41 +0900 [thread overview]
Message-ID: <bf9d1cc7-c03d-f5a8-bb96-cfcd352ac36e@opensource.wdc.com> (raw)
Message-ID: <20220629082441.U_Kdq7KNBnXAXQBLAl49Ao7soGKQIC5GMIPkBgjejIw@z> (raw)
In-Reply-To: <65e05dd1-8e92-5f6b-d68e-72987fcebf59@huawei.com>
On 6/29/22 16:43, John Garry wrote:
> 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.
Works for me.
>
> Thanks!
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-06-29 8:24 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 15:25 [PATCH v4 0/5] DMA mapping changes for SCSI core John Garry via iommu
2022-06-27 15:25 ` John Garry
2022-06-27 15:25 ` [PATCH v4 1/5] dma-mapping: Add dma_opt_mapping_size() John Garry via iommu
2022-06-27 15:25 ` John Garry
2022-06-28 11:23 ` Robin Murphy
2022-06-28 11:23 ` Robin Murphy
2022-06-28 11:27 ` John Garry via iommu
2022-06-28 11:27 ` John Garry
2022-06-29 11:57 ` John Garry via iommu
2022-06-29 11:57 ` John Garry
2022-06-27 15:25 ` [PATCH v4 2/5] dma-iommu: Add iommu_dma_opt_mapping_size() John Garry via iommu
2022-06-27 15:25 ` John Garry
2022-06-28 10:56 ` Robin Murphy
2022-06-28 10:56 ` Robin Murphy
2022-06-27 15:25 ` [PATCH v4 3/5] scsi: core: Cap shost max_sectors according to DMA mapping limits only once John Garry via iommu
2022-06-27 15:25 ` John Garry
2022-06-27 15:25 ` [PATCH v4 4/5] scsi: scsi_transport_sas: Cap shost max_sectors according to DMA optimal mapping limit John Garry via iommu
2022-06-27 15:25 ` John Garry
2022-06-27 15:25 ` [PATCH v4 5/5] libata-scsi: Cap ata_device->max_sectors according to shost->max_sectors John Garry via iommu
2022-06-27 15:25 ` John Garry
2022-06-27 23:24 ` Damien Le Moal via iommu
2022-06-27 23:24 ` Damien Le Moal
2022-06-28 7:54 ` John Garry via iommu
2022-06-28 7:54 ` John Garry
2022-06-28 9:14 ` Damien Le Moal via iommu
2022-06-28 9:14 ` Damien Le Moal
2022-06-28 11:33 ` John Garry via iommu
2022-06-28 11:33 ` John Garry
2022-06-29 5:40 ` Christoph Hellwig
2022-06-29 5:40 ` Christoph Hellwig
2022-06-29 5:58 ` Damien Le Moal via iommu
2022-06-29 5:58 ` Damien Le Moal
2022-06-29 7:43 ` John Garry via iommu
2022-06-29 7:43 ` John Garry
2022-06-29 8:24 ` Damien Le Moal via iommu [this message]
2022-06-29 8:24 ` Damien Le Moal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bf9d1cc7-c03d-f5a8-bb96-cfcd352ac36e@opensource.wdc.com \
--to=iommu@lists.linux-foundation.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jejb@linux.ibm.com \
--cc=john.garry@huawei.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox