From: Jason Gunthorpe <jgg@nvidia.com>
To: Beleswar Prasad Padhi <b-padhi@ti.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
andersson@kernel.org, afd@ti.com, nm@ti.com, hnagalla@ti.com,
Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
linux-remoteproc@vger.kernel.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] remoteproc: Use iommu_paging_domain_alloc()
Date: Mon, 23 Sep 2024 15:12:17 -0300 [thread overview]
Message-ID: <20240923181217.GF9417@nvidia.com> (raw)
In-Reply-To: <0dbde87b-593f-4b14-8929-b78e189549ad@ti.com>
On Sun, Sep 22, 2024 at 04:57:07PM +0530, Beleswar Prasad Padhi wrote:
> Since commit 17de3f5fdd35, the IOMMU framework has changed how it handles
> callback ops, moving away from using bus->iommu_ops. The omap-iommu driver
> has not yet been updated to align with these framework changes. Therefore,
> omap-iommu, and hence, omap-remoteproc have been broken since 17de3f5fdd35.
That commit is a year old now, if nobody has cared to fix or report
this can we consider removing some of this old code from upstream?
Usually a year of being broken without anyone caring is a good enough
threshold.
> Acked-by: Beleswar Padhi <b-padhi@ti.com>
Thanks
Jason
next prev parent reply other threads:[~2024-09-23 18:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 7:28 [PATCH 1/1] remoteproc: Use iommu_paging_domain_alloc() Lu Baolu
2024-08-22 16:17 ` Mathieu Poirier
2024-08-22 16:24 ` Jason Gunthorpe
2024-09-15 14:09 ` Jason Gunthorpe
2024-09-16 15:22 ` Mathieu Poirier
2024-08-29 6:17 ` Beleswar Prasad Padhi
2024-09-22 11:27 ` Beleswar Prasad Padhi
2024-09-23 18:12 ` Jason Gunthorpe [this message]
2024-09-30 16:40 ` Mathieu Poirier
2024-10-01 13:35 ` Jason Gunthorpe
2024-10-03 13:58 ` Mathieu Poirier
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=20240923181217.GF9417@nvidia.com \
--to=jgg@nvidia.com \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=b-padhi@ti.com \
--cc=baolu.lu@linux.intel.com \
--cc=hnagalla@ti.com \
--cc=iommu@lists.linux.dev \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.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 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.