From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Matthew Rosato <mjrosato@linux.ibm.com>,
iommu@lists.linux.dev, Joerg Roedel <joro@8bytes.org>,
Pierre Morel <pmorel@linux.ibm.com>,
linux-s390@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
borntraeger@linux.ibm.com, hca@linux.ibm.com, gor@linux.ibm.com,
gerald.schaefer@linux.ibm.com, agordeev@linux.ibm.com,
svens@linux.ibm.com, will@kernel.org,
Robin Murphy <robin.murphy@arm.com>,
linux-kernel@vger.kernel.org,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Sven Peter <sven@svenpeter.dev>
Subject: Re: [PATCH] iommu: Allow .iotlb_sync_map to fail and handle s390's -ENOMEM return
Date: Tue, 13 Dec 2022 14:24:37 +0100 [thread overview]
Message-ID: <74be1d4fff25840b8be2b786263c37840e5cca4c.camel@linux.ibm.com> (raw)
In-Reply-To: <Y5h6EuA+mx29pMCg@nvidia.com>
On Tue, 2022-12-13 at 09:11 -0400, Jason Gunthorpe wrote:
> On Tue, Dec 13, 2022 at 01:11:04PM +0100, Niklas Schnelle wrote:
> > --- a/drivers/iommu/tegra-gart.c
> > +++ b/drivers/iommu/tegra-gart.c
> > @@ -252,8 +252,8 @@ static int gart_iommu_of_xlate(struct device *dev,
> > return 0;
> > }
> >
> > -static void gart_iommu_sync_map(struct iommu_domain *domain, unsigned long iova,
> > - size_t size)
> > +static int gart_iommu_sync_map(struct iommu_domain *domain, unsigned long iova,
> > + size_t size)
> > {
> > FLUSH_GART_REGS(gart_handle);
> > }
>
> return 0 ?
>
> Jason
Stupid me for not at least compile testing on more platforms.
Will send a v2.
prev parent reply other threads:[~2022-12-13 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-13 12:11 [PATCH] iommu: Allow .iotlb_sync_map to fail and handle s390's -ENOMEM return Niklas Schnelle
2022-12-13 13:11 ` Jason Gunthorpe
2022-12-13 13:24 ` Niklas Schnelle [this message]
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=74be1d4fff25840b8be2b786263c37840e5cca4c.camel@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=robin.murphy@arm.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=sven@svenpeter.dev \
--cc=svens@linux.ibm.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