From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, Li Yang <leoyang.li@nxp.com>,
freedreno@lists.freedesktop.org, kvm@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
iommu@lists.linux-foundation.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 14/17] iommu: remove DOMAIN_ATTR_DMA_USE_FLUSH_QUEUE
Date: Wed, 10 Mar 2021 10:15:01 +0100 [thread overview]
Message-ID: <20210310091501.GC5928@lst.de> (raw)
In-Reply-To: <1658805c-ed28-b650-7385-a56fab3383e3@arm.com>
On Thu, Mar 04, 2021 at 03:25:27PM +0000, Robin Murphy wrote:
> On 2021-03-01 08:42, Christoph Hellwig wrote:
>> Use explicit methods for setting and querying the information instead.
>
> Now that everyone's using iommu-dma, is there any point in bouncing this
> through the drivers at all? Seems like it would make more sense for the x86
> drivers to reflect their private options back to iommu_dma_strict (and
> allow Intel's caching mode to override it as well), then have
> iommu_dma_init_domain just test !iommu_dma_strict &&
> domain->ops->flush_iotlb_all.
Hmm. I looked at this, and kill off ->dma_enable_flush_queue for
the ARM drivers and just looking at iommu_dma_strict seems like a
very clear win.
OTOH x86 is a little more complicated. AMD and intel defaul to lazy
mode, so we'd have to change the global iommu_dma_strict if they are
initialized. Also Intel has not only a "static" option to disable
lazy mode, but also a "dynamic" one where it iterates structure. So
I think on the get side we're stuck with the method, but it still
simplifies the whole thing.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: kvm@vger.kernel.org, Will Deacon <will@kernel.org>,
Joerg Roedel <joro@8bytes.org>,
linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org,
Li Yang <leoyang.li@nxp.com>,
iommu@lists.linux-foundation.org, netdev@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org,
virtualization@lists.linux-foundation.org,
freedreno@lists.freedesktop.org, Christoph Hellwig <hch@lst.de>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 14/17] iommu: remove DOMAIN_ATTR_DMA_USE_FLUSH_QUEUE
Date: Wed, 10 Mar 2021 10:15:01 +0100 [thread overview]
Message-ID: <20210310091501.GC5928@lst.de> (raw)
In-Reply-To: <1658805c-ed28-b650-7385-a56fab3383e3@arm.com>
On Thu, Mar 04, 2021 at 03:25:27PM +0000, Robin Murphy wrote:
> On 2021-03-01 08:42, Christoph Hellwig wrote:
>> Use explicit methods for setting and querying the information instead.
>
> Now that everyone's using iommu-dma, is there any point in bouncing this
> through the drivers at all? Seems like it would make more sense for the x86
> drivers to reflect their private options back to iommu_dma_strict (and
> allow Intel's caching mode to override it as well), then have
> iommu_dma_init_domain just test !iommu_dma_strict &&
> domain->ops->flush_iotlb_all.
Hmm. I looked at this, and kill off ->dma_enable_flush_queue for
the ARM drivers and just looking at iommu_dma_strict seems like a
very clear win.
OTOH x86 is a little more complicated. AMD and intel defaul to lazy
mode, so we'd have to change the global iommu_dma_strict if they are
initialized. Also Intel has not only a "static" option to disable
lazy mode, but also a "dynamic" one where it iterates structure. So
I think on the get side we're stuck with the method, but it still
simplifies the whole thing.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: kvm@vger.kernel.org, Will Deacon <will@kernel.org>,
linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org,
Li Yang <leoyang.li@nxp.com>,
iommu@lists.linux-foundation.org, netdev@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org,
Michael Ellerman <mpe@ellerman.id.au>,
virtualization@lists.linux-foundation.org,
freedreno@lists.freedesktop.org, Christoph Hellwig <hch@lst.de>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 14/17] iommu: remove DOMAIN_ATTR_DMA_USE_FLUSH_QUEUE
Date: Wed, 10 Mar 2021 10:15:01 +0100 [thread overview]
Message-ID: <20210310091501.GC5928@lst.de> (raw)
In-Reply-To: <1658805c-ed28-b650-7385-a56fab3383e3@arm.com>
On Thu, Mar 04, 2021 at 03:25:27PM +0000, Robin Murphy wrote:
> On 2021-03-01 08:42, Christoph Hellwig wrote:
>> Use explicit methods for setting and querying the information instead.
>
> Now that everyone's using iommu-dma, is there any point in bouncing this
> through the drivers at all? Seems like it would make more sense for the x86
> drivers to reflect their private options back to iommu_dma_strict (and
> allow Intel's caching mode to override it as well), then have
> iommu_dma_init_domain just test !iommu_dma_strict &&
> domain->ops->flush_iotlb_all.
Hmm. I looked at this, and kill off ->dma_enable_flush_queue for
the ARM drivers and just looking at iommu_dma_strict seems like a
very clear win.
OTOH x86 is a little more complicated. AMD and intel defaul to lazy
mode, so we'd have to change the global iommu_dma_strict if they are
initialized. Also Intel has not only a "static" option to disable
lazy mode, but also a "dynamic" one where it iterates structure. So
I think on the get side we're stuck with the method, but it still
simplifies the whole thing.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: kvm@vger.kernel.org, Will Deacon <will@kernel.org>,
Joerg Roedel <joro@8bytes.org>,
linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org,
Li Yang <leoyang.li@nxp.com>,
iommu@lists.linux-foundation.org, netdev@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org,
Michael Ellerman <mpe@ellerman.id.au>,
virtualization@lists.linux-foundation.org,
freedreno@lists.freedesktop.org, Christoph Hellwig <hch@lst.de>,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 14/17] iommu: remove DOMAIN_ATTR_DMA_USE_FLUSH_QUEUE
Date: Wed, 10 Mar 2021 10:15:01 +0100 [thread overview]
Message-ID: <20210310091501.GC5928@lst.de> (raw)
In-Reply-To: <1658805c-ed28-b650-7385-a56fab3383e3@arm.com>
On Thu, Mar 04, 2021 at 03:25:27PM +0000, Robin Murphy wrote:
> On 2021-03-01 08:42, Christoph Hellwig wrote:
>> Use explicit methods for setting and querying the information instead.
>
> Now that everyone's using iommu-dma, is there any point in bouncing this
> through the drivers at all? Seems like it would make more sense for the x86
> drivers to reflect their private options back to iommu_dma_strict (and
> allow Intel's caching mode to override it as well), then have
> iommu_dma_init_domain just test !iommu_dma_strict &&
> domain->ops->flush_iotlb_all.
Hmm. I looked at this, and kill off ->dma_enable_flush_queue for
the ARM drivers and just looking at iommu_dma_strict seems like a
very clear win.
OTOH x86 is a little more complicated. AMD and intel defaul to lazy
mode, so we'd have to change the global iommu_dma_strict if they are
initialized. Also Intel has not only a "static" option to disable
lazy mode, but also a "dynamic" one where it iterates structure. So
I think on the get side we're stuck with the method, but it still
simplifies the whole thing.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>, Li Yang <leoyang.li@nxp.com>,
freedreno@lists.freedesktop.org, kvm@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>,
linuxppc-dev@lists.ozlabs.org, dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
iommu@lists.linux-foundation.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
David Woodhouse <dwmw2@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 14/17] iommu: remove DOMAIN_ATTR_DMA_USE_FLUSH_QUEUE
Date: Wed, 10 Mar 2021 10:15:01 +0100 [thread overview]
Message-ID: <20210310091501.GC5928@lst.de> (raw)
In-Reply-To: <1658805c-ed28-b650-7385-a56fab3383e3@arm.com>
On Thu, Mar 04, 2021 at 03:25:27PM +0000, Robin Murphy wrote:
> On 2021-03-01 08:42, Christoph Hellwig wrote:
>> Use explicit methods for setting and querying the information instead.
>
> Now that everyone's using iommu-dma, is there any point in bouncing this
> through the drivers at all? Seems like it would make more sense for the x86
> drivers to reflect their private options back to iommu_dma_strict (and
> allow Intel's caching mode to override it as well), then have
> iommu_dma_init_domain just test !iommu_dma_strict &&
> domain->ops->flush_iotlb_all.
Hmm. I looked at this, and kill off ->dma_enable_flush_queue for
the ARM drivers and just looking at iommu_dma_strict seems like a
very clear win.
OTOH x86 is a little more complicated. AMD and intel defaul to lazy
mode, so we'd have to change the global iommu_dma_strict if they are
initialized. Also Intel has not only a "static" option to disable
lazy mode, but also a "dynamic" one where it iterates structure. So
I think on the get side we're stuck with the method, but it still
simplifies the whole thing.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-10 9:15 UTC|newest]
Thread overview: 207+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 8:42 cleanup unused or almost unused IOMMU APIs and the FSL PAMU driver Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 01/17] iommu: remove the unused domain_window_disable method Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 02/17] iommu/fsl_pamu: remove fsl_pamu_get_domain_attr Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 03/17] iommu/fsl_pamu: remove support for setting DOMAIN_ATTR_GEOMETRY Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 04/17] iommu/fsl_pamu: merge iommu_alloc_dma_domain into fsl_pamu_domain_alloc Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 05/17] iommu/fsl_pamu: remove support for multiple windows Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 06/17] iommu/fsl_pamu: remove ->domain_window_enable Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 07/17] iommu/fsl_pamu: replace DOMAIN_ATTR_FSL_PAMU_STASH with a direct call Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 08/17] iommu/fsl_pamu: merge pamu_set_liodn and map_liodn Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 09/17] iommu/fsl_pamu: merge handle_attach_device into fsl_pamu_attach_device Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 10/17] iommu/fsl_pamu: enable the liodn when attaching a device Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 11/17] iommu/fsl_pamu: remove the snoop_id field Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 12/17] iommu: remove DOMAIN_ATTR_PAGING Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 13/17] iommu: remove DOMAIN_ATTR_GEOMETRY Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 14/17] iommu: remove DOMAIN_ATTR_DMA_USE_FLUSH_QUEUE Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-04 15:25 ` Robin Murphy
2021-03-04 15:25 ` Robin Murphy
2021-03-04 15:25 ` Robin Murphy
2021-03-04 15:25 ` Robin Murphy
2021-03-04 15:25 ` Robin Murphy
2021-03-04 15:25 ` Robin Murphy
2021-03-10 8:54 ` Christoph Hellwig
2021-03-10 8:54 ` Christoph Hellwig
2021-03-10 8:54 ` Christoph Hellwig
2021-03-10 8:54 ` Christoph Hellwig
2021-03-10 8:54 ` Christoph Hellwig
2021-03-10 9:15 ` Christoph Hellwig [this message]
2021-03-10 9:15 ` Christoph Hellwig
2021-03-10 9:15 ` Christoph Hellwig
2021-03-10 9:15 ` Christoph Hellwig
2021-03-10 9:15 ` Christoph Hellwig
2021-03-10 9:25 ` Christoph Hellwig
2021-03-10 9:25 ` Christoph Hellwig
2021-03-10 9:25 ` Christoph Hellwig
2021-03-10 9:25 ` Christoph Hellwig
2021-03-10 9:25 ` Christoph Hellwig
2021-03-10 18:39 ` Robin Murphy
2021-03-10 18:39 ` Robin Murphy
2021-03-10 18:39 ` Robin Murphy
2021-03-10 18:39 ` Robin Murphy
2021-03-10 18:39 ` Robin Murphy
2021-03-10 18:39 ` Robin Murphy
2021-03-11 8:26 ` Christoph Hellwig
2021-03-11 8:26 ` Christoph Hellwig
2021-03-11 8:26 ` Christoph Hellwig
2021-03-11 8:26 ` Christoph Hellwig
2021-03-11 8:26 ` Christoph Hellwig
2021-03-12 16:18 ` Robin Murphy
2021-03-12 16:18 ` Robin Murphy
2021-03-12 16:18 ` Robin Murphy
2021-03-12 16:18 ` Robin Murphy
2021-03-12 16:18 ` Robin Murphy
2021-03-12 16:18 ` Robin Murphy
2021-03-15 8:33 ` Christoph Hellwig
2021-03-15 8:33 ` Christoph Hellwig
2021-03-15 8:33 ` Christoph Hellwig
2021-03-15 8:33 ` Christoph Hellwig
2021-03-15 8:33 ` Christoph Hellwig
2021-03-16 13:03 ` Robin Murphy
2021-03-16 13:03 ` Robin Murphy
2021-03-16 13:03 ` Robin Murphy
2021-03-16 13:03 ` Robin Murphy
2021-03-16 13:03 ` Robin Murphy
2021-03-16 13:03 ` Robin Murphy
2021-03-01 8:42 ` [PATCH 15/17] iommu: remove DOMAIN_ATTR_NESTING Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-14 10:44 ` Auger Eric
2021-03-14 10:44 ` Auger Eric
2021-03-14 10:44 ` Auger Eric
2021-03-14 10:44 ` Auger Eric
2021-03-14 10:44 ` Auger Eric
2021-03-14 10:44 ` Auger Eric
2021-03-14 15:58 ` Christoph Hellwig
2021-03-14 15:58 ` Christoph Hellwig
2021-03-14 15:58 ` Christoph Hellwig
2021-03-14 15:58 ` Christoph Hellwig
2021-03-14 15:58 ` Christoph Hellwig
2021-03-15 7:52 ` Auger Eric
2021-03-15 7:52 ` Auger Eric
2021-03-15 7:52 ` Auger Eric
2021-03-15 7:52 ` Auger Eric
2021-03-15 7:52 ` Auger Eric
2021-03-15 7:52 ` Auger Eric
2021-03-25 6:12 ` Tian, Kevin
2021-03-25 6:12 ` Tian, Kevin
2021-03-25 6:12 ` Tian, Kevin
2021-03-25 6:12 ` Tian, Kevin
2021-03-25 6:12 ` Tian, Kevin
2021-03-25 6:12 ` Tian, Kevin
2021-03-25 6:51 ` Christoph Hellwig
2021-03-25 6:51 ` Christoph Hellwig
2021-03-25 6:51 ` Christoph Hellwig
2021-03-25 6:51 ` Christoph Hellwig
2021-03-25 6:51 ` Christoph Hellwig
2021-03-01 8:42 ` [PATCH 16/17] iommu: remove DOMAIN_ATTR_IO_PGTABLE_CFG Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-04 15:48 ` Robin Murphy
2021-03-04 15:48 ` Robin Murphy
2021-03-04 15:48 ` Robin Murphy
2021-03-04 15:48 ` Robin Murphy
2021-03-04 15:48 ` Robin Murphy
2021-03-04 15:48 ` Robin Murphy
2021-03-04 23:11 ` [Freedreno] " Rob Clark
2021-03-04 23:11 ` Rob Clark
2021-03-04 23:11 ` Rob Clark
2021-03-04 23:11 ` Rob Clark
2021-03-04 23:11 ` Rob Clark
2021-03-04 23:11 ` Rob Clark
2021-03-05 10:00 ` Will Deacon
2021-03-05 10:00 ` Will Deacon
2021-03-05 10:00 ` Will Deacon
2021-03-05 10:00 ` Will Deacon
2021-03-05 10:00 ` Will Deacon
2021-03-05 10:00 ` Will Deacon
2021-03-10 8:58 ` Christoph Hellwig
2021-03-10 8:58 ` Christoph Hellwig
2021-03-10 8:58 ` Christoph Hellwig
2021-03-10 8:58 ` Christoph Hellwig
2021-03-10 8:58 ` Christoph Hellwig
2021-03-10 10:55 ` Will Deacon
2021-03-10 10:55 ` Will Deacon
2021-03-10 10:55 ` Will Deacon
2021-03-10 10:55 ` Will Deacon
2021-03-10 10:55 ` Will Deacon
2021-03-10 10:55 ` Will Deacon
2021-03-01 8:42 ` [PATCH 17/17] iommu: remove iommu_domain_set_attr Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-01 8:42 ` Christoph Hellwig
2021-03-04 11:10 ` cleanup unused or almost unused IOMMU APIs and the FSL PAMU driver Joerg Roedel
2021-03-04 11:10 ` Joerg Roedel
2021-03-04 11:10 ` Joerg Roedel
2021-03-04 11:10 ` Joerg Roedel
2021-03-04 11:10 ` Joerg Roedel
2021-03-04 11:10 ` Joerg Roedel
2021-03-06 0:03 ` Li Yang
2021-03-06 0:03 ` Li Yang
2021-03-06 0:03 ` Li Yang
2021-03-06 0:03 ` Li Yang
2021-03-06 0:03 ` Li Yang
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=20210310091501.GC5928@lst.de \
--to=hch@lst.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=dwmw2@infradead.org \
--cc=freedreno@lists.freedesktop.org \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=virtualization@lists.linux-foundation.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.