All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	ath10k@lists.infradead.org, ath11k@lists.infradead.org,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	linux-s390@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-tegra@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 1/8] iommu: Add a gfp parameter to iommu_map()
Date: Fri, 20 Jan 2023 13:53:40 -0400	[thread overview]
Message-ID: <Y8rVJGyTKAjXjLwV@nvidia.com> (raw)
In-Reply-To: <Y8pd50mdNShTyVRX@8bytes.org>

On Fri, Jan 20, 2023 at 10:24:55AM +0100, Joerg Roedel wrote:
> On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote:
> > I think it is just better to follow kernel convention and have
> > allocation functions include the GFP because it is a clear signal to
> > the user that there is an allocation hidden inside the API. The whole
> > point of gfp is not to have multitudes of every function for every
> > allocation mode.
> 
> Well, having GFP parameters is not a strict kernel convention. There are
> places doing it differently and have sleeping and atomic variants of
> APIs. I have to say I like the latter more. But given that this leads to
> an invasion of API functions here which all do the same under the hood, I
> agree it is better to go with a GFP parameter here.

Ok, I think we are done with this series, I'll stick it in linux-next
for a bit and send you a PR so the trees stay in sync

Thanks,
Jason

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	ath10k@lists.infradead.org, ath11k@lists.infradead.org,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	linux-s390@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-tegra@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 1/8] iommu: Add a gfp parameter to iommu_map()
Date: Fri, 20 Jan 2023 13:53:40 -0400	[thread overview]
Message-ID: <Y8rVJGyTKAjXjLwV@nvidia.com> (raw)
In-Reply-To: <Y8pd50mdNShTyVRX@8bytes.org>

On Fri, Jan 20, 2023 at 10:24:55AM +0100, Joerg Roedel wrote:
> On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote:
> > I think it is just better to follow kernel convention and have
> > allocation functions include the GFP because it is a clear signal to
> > the user that there is an allocation hidden inside the API. The whole
> > point of gfp is not to have multitudes of every function for every
> > allocation mode.
> 
> Well, having GFP parameters is not a strict kernel convention. There are
> places doing it differently and have sleeping and atomic variants of
> APIs. I have to say I like the latter more. But given that this leads to
> an invasion of API functions here which all do the same under the hood, I
> agree it is better to go with a GFP parameter here.

Ok, I think we are done with this series, I'll stick it in linux-next
for a bit and send you a PR so the trees stay in sync

Thanks,
Jason

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	ath10k@lists.infradead.org, ath11k@lists.infradead.org,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	linux-s390@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-tegra@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 1/8] iommu: Add a gfp parameter to iommu_map()
Date: Fri, 20 Jan 2023 13:53:40 -0400	[thread overview]
Message-ID: <Y8rVJGyTKAjXjLwV@nvidia.com> (raw)
In-Reply-To: <Y8pd50mdNShTyVRX@8bytes.org>

On Fri, Jan 20, 2023 at 10:24:55AM +0100, Joerg Roedel wrote:
> On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote:
> > I think it is just better to follow kernel convention and have
> > allocation functions include the GFP because it is a clear signal to
> > the user that there is an allocation hidden inside the API. The whole
> > point of gfp is not to have multitudes of every function for every
> > allocation mode.
> 
> Well, having GFP parameters is not a strict kernel convention. There are
> places doing it differently and have sleeping and atomic variants of
> APIs. I have to say I like the latter more. But given that this leads to
> an invasion of API functions here which all do the same under the hood, I
> agree it is better to go with a GFP parameter here.

Ok, I think we are done with this series, I'll stick it in linux-next
for a bit and send you a PR so the trees stay in sync

Thanks,
Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: kvm@vger.kernel.org, nouveau@lists.freedesktop.org,
	linux-remoteproc@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-s390@vger.kernel.org,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	linux-rdma@vger.kernel.org, ath10k@lists.infradead.org,
	iommu@lists.linux.dev,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	ath11k@lists.infradead.org, linux-media@vger.kernel.org,
	Kevin Tian <kevin.tian@intel.com>,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	linux-arm-msm@vger.kernel.org,
	Alex Williamson <alex.williamson@redhat.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org,
	Robin Murphy <robin.murphy@arm.com>,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [Nouveau] [PATCH 1/8] iommu: Add a gfp parameter to iommu_map()
Date: Fri, 20 Jan 2023 13:53:40 -0400	[thread overview]
Message-ID: <Y8rVJGyTKAjXjLwV@nvidia.com> (raw)
In-Reply-To: <Y8pd50mdNShTyVRX@8bytes.org>

On Fri, Jan 20, 2023 at 10:24:55AM +0100, Joerg Roedel wrote:
> On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote:
> > I think it is just better to follow kernel convention and have
> > allocation functions include the GFP because it is a clear signal to
> > the user that there is an allocation hidden inside the API. The whole
> > point of gfp is not to have multitudes of every function for every
> > allocation mode.
> 
> Well, having GFP parameters is not a strict kernel convention. There are
> places doing it differently and have sleeping and atomic variants of
> APIs. I have to say I like the latter more. But given that this leads to
> an invasion of API functions here which all do the same under the hood, I
> agree it is better to go with a GFP parameter here.

Ok, I think we are done with this series, I'll stick it in linux-next
for a bit and send you a PR so the trees stay in sync

Thanks,
Jason

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: Robin Murphy <robin.murphy@arm.com>,
	Lu Baolu <baolu.lu@linux.intel.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	ath10k@lists.infradead.org, ath11k@lists.infradead.org,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	dri-devel@lists.freedesktop.org, iommu@lists.linux.dev,
	kvm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	linux-s390@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-tegra@vger.kernel.org, linux-wireless@vger.kernel.org,
	netdev@vger.kernel.org, nouveau@lists.freedesktop.org,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 1/8] iommu: Add a gfp parameter to iommu_map()
Date: Fri, 20 Jan 2023 13:53:40 -0400	[thread overview]
Message-ID: <Y8rVJGyTKAjXjLwV@nvidia.com> (raw)
In-Reply-To: <Y8pd50mdNShTyVRX@8bytes.org>

On Fri, Jan 20, 2023 at 10:24:55AM +0100, Joerg Roedel wrote:
> On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote:
> > I think it is just better to follow kernel convention and have
> > allocation functions include the GFP because it is a clear signal to
> > the user that there is an allocation hidden inside the API. The whole
> > point of gfp is not to have multitudes of every function for every
> > allocation mode.
> 
> Well, having GFP parameters is not a strict kernel convention. There are
> places doing it differently and have sleeping and atomic variants of
> APIs. I have to say I like the latter more. But given that this leads to
> an invasion of API functions here which all do the same under the hood, I
> agree it is better to go with a GFP parameter here.

Ok, I think we are done with this series, I'll stick it in linux-next
for a bit and send you a PR so the trees stay in sync

Thanks,
Jason

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: Joerg Roedel <joro@8bytes.org>
Cc: kvm@vger.kernel.org, nouveau@lists.freedesktop.org,
	linux-remoteproc@vger.kernel.org,
	dri-devel@lists.freedesktop.org,
	virtualization@lists.linux-foundation.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-s390@vger.kernel.org,
	Matthew Rosato <mjrosato@linux.ibm.com>,
	linux-rdma@vger.kernel.org, ath10k@lists.infradead.org,
	iommu@lists.linux.dev,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	ath11k@lists.infradead.org, linux-media@vger.kernel.org,
	Kevin Tian <kevin.tian@intel.com>,
	Niklas Schnelle <schnelle@linux.ibm.com>,
	linux-arm-msm@vger.kernel.org,
	Alex Williamson <alex.williamson@redhat.com>,
	linux-tegra@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
	linux-wireless@vger.kernel.org,
	Robin Murphy <robin.murphy@arm.com>,
	Lu Baolu <baolu.lu@linux.intel.com>
Subject: Re: [PATCH 1/8] iommu: Add a gfp parameter to iommu_map()
Date: Fri, 20 Jan 2023 13:53:40 -0400	[thread overview]
Message-ID: <Y8rVJGyTKAjXjLwV@nvidia.com> (raw)
In-Reply-To: <Y8pd50mdNShTyVRX@8bytes.org>

On Fri, Jan 20, 2023 at 10:24:55AM +0100, Joerg Roedel wrote:
> On Fri, Jan 06, 2023 at 01:24:11PM -0400, Jason Gunthorpe wrote:
> > I think it is just better to follow kernel convention and have
> > allocation functions include the GFP because it is a clear signal to
> > the user that there is an allocation hidden inside the API. The whole
> > point of gfp is not to have multitudes of every function for every
> > allocation mode.
> 
> Well, having GFP parameters is not a strict kernel convention. There are
> places doing it differently and have sleeping and atomic variants of
> APIs. I have to say I like the latter more. But given that this leads to
> an invasion of API functions here which all do the same under the hood, I
> agree it is better to go with a GFP parameter here.

Ok, I think we are done with this series, I'll stick it in linux-next
for a bit and send you a PR so the trees stay in sync

Thanks,
Jason

  reply	other threads:[~2023-01-20 17:54 UTC|newest]

Thread overview: 144+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 16:42 [PATCH 0/8] Let iommufd charge IOPTE allocations to the memory cgroup Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` Jason Gunthorpe
2023-01-06 16:42 ` [PATCH 1/8] iommu: Add a gfp parameter to iommu_map() Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 17:15   ` Robin Murphy
2023-01-06 17:15     ` Robin Murphy
2023-01-06 17:15     ` Robin Murphy
2023-01-06 17:15     ` Robin Murphy
2023-01-06 17:15     ` [Nouveau] " Robin Murphy
2023-01-06 17:15     ` Robin Murphy
2023-01-06 17:15     ` Robin Murphy
2023-01-06 17:24     ` Jason Gunthorpe
2023-01-06 17:24       ` Jason Gunthorpe
2023-01-06 17:24       ` Jason Gunthorpe
2023-01-06 17:24       ` [Nouveau] " Jason Gunthorpe
2023-01-06 17:24       ` Jason Gunthorpe
2023-01-06 17:24       ` Jason Gunthorpe
2023-01-20  9:24       ` Joerg Roedel
2023-01-20  9:24         ` Joerg Roedel
2023-01-20  9:24         ` Joerg Roedel
2023-01-20  9:24         ` Joerg Roedel
2023-01-20  9:24         ` [Nouveau] " Joerg Roedel
2023-01-20  9:24         ` Joerg Roedel
2023-01-20  9:24         ` Joerg Roedel
2023-01-20 17:53         ` Jason Gunthorpe [this message]
2023-01-20 17:53           ` Jason Gunthorpe
2023-01-20 17:53           ` Jason Gunthorpe
2023-01-20 17:53           ` [Nouveau] " Jason Gunthorpe
2023-01-20 17:53           ` Jason Gunthorpe
2023-01-20 17:53           ` Jason Gunthorpe
2023-01-23  9:59           ` Joerg Roedel
2023-01-23  9:59             ` Joerg Roedel
2023-01-23  9:59             ` Joerg Roedel
2023-01-23  9:59             ` Joerg Roedel
2023-01-23  9:59             ` [Nouveau] " Joerg Roedel
2023-01-23  9:59             ` Joerg Roedel
2023-01-23  9:59             ` Joerg Roedel
2023-01-16 18:12     ` Jason Gunthorpe
2023-01-16 18:12       ` Jason Gunthorpe
2023-01-16 18:12       ` Jason Gunthorpe
2023-01-16 18:12       ` [Nouveau] " Jason Gunthorpe
2023-01-16 18:12       ` Jason Gunthorpe
2023-01-16 18:12       ` Jason Gunthorpe
2023-01-06 16:42 ` [PATCH 2/8] iommu: Remove iommu_map_atomic() Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42 ` [PATCH 3/8] iommu: Add a gfp parameter to iommu_map_sg() Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42 ` [PATCH 4/8] iommu/dma: Use the gfp parameter in __iommu_dma_alloc_noncontiguous() Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42 ` [PATCH 5/8] iommufd: Use GFP_KERNEL_ACCOUNT for iommu_map() Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42 ` [PATCH 6/8] iommu/intel: Add a gfp parameter to alloc_pgtable_page() Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-17  3:35   ` Tian, Kevin
2023-01-17  3:35     ` Tian, Kevin
2023-01-17  3:35     ` Tian, Kevin
2023-01-17  3:35     ` Tian, Kevin
2023-01-17  3:35     ` [Nouveau] " Tian, Kevin
2023-01-17  3:35     ` Tian, Kevin
2023-01-17  3:35     ` Tian, Kevin
2023-01-17 13:30     ` Jason Gunthorpe
2023-01-17 13:30       ` Jason Gunthorpe
2023-01-17 13:30       ` Jason Gunthorpe
2023-01-17 13:30       ` [Nouveau] " Jason Gunthorpe
2023-01-17 13:30       ` Jason Gunthorpe
2023-01-17 13:30       ` Jason Gunthorpe
2023-01-18  1:18       ` Tian, Kevin
2023-01-18  1:18         ` Tian, Kevin
2023-01-18  1:18         ` Tian, Kevin
2023-01-18  1:18         ` Tian, Kevin
2023-01-18  1:18         ` [Nouveau] " Tian, Kevin
2023-01-18  1:18         ` Tian, Kevin
2023-01-18  1:18         ` Tian, Kevin
2023-01-18 15:15         ` Jason Gunthorpe
2023-01-18 15:15           ` Jason Gunthorpe
2023-01-18 15:15           ` Jason Gunthorpe
2023-01-18 15:15           ` [Nouveau] " Jason Gunthorpe
2023-01-18 15:15           ` Jason Gunthorpe
2023-01-18 15:15           ` Jason Gunthorpe
2023-01-06 16:42 ` [PATCH 7/8] iommu/intel: Support the gfp argument to the map_pages op Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-17  3:38   ` Tian, Kevin
2023-01-17  3:38     ` Tian, Kevin
2023-01-17  3:38     ` Tian, Kevin
2023-01-17  3:38     ` Tian, Kevin
2023-01-17  3:38     ` [Nouveau] " Tian, Kevin
2023-01-17  3:38     ` Tian, Kevin
2023-01-17  3:38     ` Tian, Kevin
2023-01-17  8:35     ` Baolu Lu
2023-01-17  8:35       ` Baolu Lu
2023-01-17  8:35       ` Baolu Lu
2023-01-17  8:35       ` [Nouveau] " Baolu Lu
2023-01-17  8:35       ` Baolu Lu
2023-01-17  8:35       ` Baolu Lu
2023-01-17 13:28     ` Jason Gunthorpe
2023-01-17 13:28       ` Jason Gunthorpe
2023-01-17 13:28       ` Jason Gunthorpe
2023-01-17 13:28       ` [Nouveau] " Jason Gunthorpe
2023-01-17 13:28       ` Jason Gunthorpe
2023-01-17 13:28       ` Jason Gunthorpe
2023-01-06 16:42 ` [PATCH 8/8] iommu/s390: Push the gfp parameter to the kmem_cache_alloc()'s Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` [Nouveau] " Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-06 16:42   ` Jason Gunthorpe
2023-01-17  8:49   ` Niklas Schnelle
2023-01-17  8:49     ` Niklas Schnelle
2023-01-17  8:49     ` Niklas Schnelle
2023-01-17  8:49     ` [Nouveau] " Niklas Schnelle
2023-01-17  8:49     ` Niklas Schnelle
2023-01-17  8:49     ` Niklas Schnelle

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=Y8rVJGyTKAjXjLwV@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=ath10k@lists.infradead.org \
    --cc=ath11k@lists.infradead.org \
    --cc=baolu.lu@linux.intel.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=iommu@lists.linux.dev \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mjrosato@linux.ibm.com \
    --cc=netdev@vger.kernel.org \
    --cc=nouveau@lists.freedesktop.org \
    --cc=robin.murphy@arm.com \
    --cc=schnelle@linux.ibm.com \
    --cc=virtualization@lists.linux-foundation.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.