From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] iommu: convert DT component matching to component_match_add_release()
Date: Thu, 10 Nov 2016 12:25:41 +0100 [thread overview]
Message-ID: <20161110112541.GB9996@8bytes.org> (raw)
In-Reply-To: <E1bwo8o-0005LV-54@rmk-PC.armlinux.org.uk>
On Wed, Oct 19, 2016 at 11:30:34AM +0100, Russell King wrote:
> Convert DT component matching to use component_match_add_release().
>
> Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> ---
> drivers/iommu/mtk_iommu.c | 8 +++++---
> drivers/iommu/mtk_iommu.h | 5 +++++
> drivers/iommu/mtk_iommu_v1.c | 8 +++++---
> 3 files changed, 15 insertions(+), 6 deletions(-)
Applied, thanks.
next prev parent reply other threads:[~2016-11-10 11:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 10:30 [PATCH] iommu: convert DT component matching to component_match_add_release() Russell King
2016-11-10 11:25 ` Joerg Roedel [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-03 7:58 Russell King
2016-06-03 13:13 ` Matthias Brugger
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=20161110112541.GB9996@8bytes.org \
--to=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).