From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Joerg Roedel <joro@8bytes•org>, Russell King <rmk@armlinux•org.uk>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Honghui Zhang <honghui.zhang@mediatek•com>
Subject: linux-next: manual merge of the iommu tree with the arm tree
Date: Tue, 28 Jun 2016 13:13:10 +1000 [thread overview]
Message-ID: <20160628131310.5bf6ebd6@canb.auug.org.au> (raw)
Hi Joerg,
Today's linux-next merge of the iommu tree got a conflict in:
drivers/iommu/mtk_iommu.c
between commit:
d267804c8457 ("iommu: convert DT component matching to component_match_add_release()")
from the arm tree and commit:
9ca340c98c0d ("iommu/mediatek: move the common struct into header file")
from the iommu tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc drivers/iommu/mtk_iommu.c
index c036df1c49ca,b12c12d74c33..000000000000
--- a/drivers/iommu/mtk_iommu.c
+++ b/drivers/iommu/mtk_iommu.c
@@@ -552,30 -524,6 +524,11 @@@ static int mtk_iommu_hw_init(const stru
return 0;
}
- static int compare_of(struct device *dev, void *data)
- {
- return dev->of_node == data;
- }
-
+static void release_of(struct device *dev, void *data)
+{
+ of_node_put(data);
+}
+
- static int mtk_iommu_bind(struct device *dev)
- {
- struct mtk_iommu_data *data = dev_get_drvdata(dev);
-
- return component_bind_all(dev, &data->smi_imu);
- }
-
- static void mtk_iommu_unbind(struct device *dev)
- {
- struct mtk_iommu_data *data = dev_get_drvdata(dev);
-
- component_unbind_all(dev, &data->smi_imu);
- }
-
static const struct component_master_ops mtk_iommu_com_ops = {
.bind = mtk_iommu_bind,
.unbind = mtk_iommu_unbind,
next reply other threads:[~2016-06-28 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 3:13 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-06-20 3:20 linux-next: manual merge of the iommu tree with the arm tree Stephen Rothwell
2016-06-20 8:02 ` Russell King
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=20160628131310.5bf6ebd6@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=honghui.zhang@mediatek$(echo .)com \
--cc=joro@8bytes$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rmk@armlinux$(echo .)org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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