From: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
To: Suman Anna <s-anna-l0cyMroinI0@public.gmane.org>
Cc: linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH 0/2] Add missing #iommu-cells on IOMMU nodes
Date: Tue, 14 Jul 2015 00:01:40 -0700 [thread overview]
Message-ID: <20150714070140.GF17550@atomide.com> (raw)
In-Reply-To: <1436549336-33456-1-git-send-email-s-anna-l0cyMroinI0@public.gmane.org>
* Suman Anna <s-anna-l0cyMroinI0@public.gmane.org> [150710 10:31]:
> Hi Tony,
>
> This series adds the #iommu-cells property to the existing
> IOMMU nodes on OMAP4 & OMAP5. It was already fixed for OMAP3
> in commit 2055088b5e17 ("ARM: dts: omap3: Add #iommu-cells to
> isp and iva iommu").
>
> OMAP4 and OMAP5 do not yet have users for these IOMMUs (remoteproc
> nodes), so the warning as seen with the fix added for OMAP3 is not
> seen yet, but will as soon as a user is added.
Applying both into omap-for-v4.2/fixes thanks.
Tony
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-07-14 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 17:28 [PATCH 0/2] Add missing #iommu-cells on IOMMU nodes Suman Anna
[not found] ` <1436549336-33456-1-git-send-email-s-anna-l0cyMroinI0@public.gmane.org>
2015-07-10 17:28 ` [PATCH 1/2] ARM: dts: OMAP4: Add #iommu-cells property to IOMMUs Suman Anna
2015-07-10 17:28 ` [PATCH 2/2] ARM: dts: OMAP5: " Suman Anna
2015-07-14 7:01 ` Tony Lindgren [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=20150714070140.GF17550@atomide.com \
--to=tony-4v6ys6ai5vpbdgjk7y7tuq@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=s-anna-l0cyMroinI0@public.gmane.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).