From: Will Deacon <will@kernel.org>
To: Rob Clark <robdclark@gmail.com>,
Amey Narkhede <ameynarkhede03@gmail.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Sai Prakash Ranjan <saiprakash.ranjan@codeaurora.org>,
linux-kernel@vger.kernel.org, Joerg Roedel <joro@8bytes.org>,
Zenghui Yu <yuzenghui@huawei.com>,
Barry Song <song.bao.hua@hisilicon.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>,
linux-arm-msm@vger.kernel.org,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Krishna Reddy <vdumpa@nvidia.com>,
iommu@lists.linux-foundation.org,
Robin Murphy <robin.murphy@arm.com>,
Jon Hunter <jonathanh@nvidia.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] iommu/arm: Cleanup resources in case of probe error path
Date: Tue, 8 Jun 2021 18:16:47 +0100 [thread overview]
Message-ID: <162317119382.2860700.13290595260136409197.b4-ty@kernel.org> (raw)
In-Reply-To: <20210608164559.204023-1-ameynarkhede03@gmail.com>
On Tue, 8 Jun 2021 22:15:59 +0530, Amey Narkhede wrote:
> If device registration fails, remove sysfs attribute
> and if setting bus callbacks fails, unregister the device
> and cleanup the sysfs attribute.
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/1] iommu/arm: Cleanup resources in case of probe error path
https://git.kernel.org/will/c/249c9dc6aa0d
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
next prev parent reply other threads:[~2021-06-08 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 16:45 [PATCH] iommu/arm: Cleanup resources in case of probe error path Amey Narkhede
2021-06-08 17:16 ` Will Deacon [this message]
[not found] ` <CGME20210630124816eucas1p27563f0a456c0196e20937619aa2f8d26@eucas1p2.samsung.com>
2021-06-30 12:48 ` Marek Szyprowski
2021-06-30 12:59 ` Will Deacon
2021-06-30 13:48 ` Marek Szyprowski
2021-06-30 14:01 ` Robin Murphy
2021-07-01 8:29 ` Marek Szyprowski
2021-07-01 9:01 ` Will Deacon
2021-07-01 9:11 ` Robin Murphy
2021-07-01 9:26 ` Marek Szyprowski
2021-07-01 0:13 ` Krishna Reddy
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=162317119382.2860700.13290595260136409197.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=ameynarkhede03@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=song.bao.hua@hisilicon.com \
--cc=vdumpa@nvidia.com \
--cc=yuzenghui@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).