From: Tony Lindgren <tony@atomide.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Tero Kristo <t-kristo@ti.com>
Subject: Re: [PATCH 0/5] ARM: dts: omap: Fix some DTC warnings
Date: Mon, 11 Apr 2016 12:39:54 -0700 [thread overview]
Message-ID: <20160411193954.GB5995@atomide.com> (raw)
In-Reply-To: <20160401203812.GP9329@atomide.com>
* Tony Lindgren <tony@atomide.com> [160401 13:39]:
> * Javier Martinez Canillas <javier@osg.samsung.com> [160401 13:21]:
> > Hello Tony
> >
> > DTC reports a lot of warnings on omap DTS due a mismatch between unit
> > names and reg properties in different device nodes. This series tries
> > to fix at least some of them, but there are still a lot remaining.
>
> Great, adding Tero to Cc as I think he is already looking at fixing
> the clock related warnings.
OK adding these finally into omap-for-v4.7/dt thanks.
Tony
prev parent reply other threads:[~2016-04-11 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 20:20 [PATCH 0/5] ARM: dts: omap: Fix some DTC warnings Javier Martinez Canillas
2016-04-01 20:20 ` [PATCH 1/5] ARM: dts: omap: add missing unit name to pbias regulator nodes Javier Martinez Canillas
2016-04-01 20:20 ` [PATCH 2/5] ARM: dts: n8x0: remove unneeded unit name for i2c node Javier Martinez Canillas
2016-04-01 20:20 ` [PATCH 3/5] ARM: dts: omap3: add missing unit name to PMU node Javier Martinez Canillas
2016-04-01 20:20 ` [PATCH 4/5] ARM: dts: omap: remove unneeded unit name for sound nodes Javier Martinez Canillas
2016-04-01 20:20 ` [PATCH 5/5] ARM: dts: omap: add missing unit names to bandgap nodes Javier Martinez Canillas
2016-04-01 20:38 ` [PATCH 0/5] ARM: dts: omap: Fix some DTC warnings Tony Lindgren
2016-04-11 19:39 ` 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=20160411193954.GB5995@atomide.com \
--to=tony@atomide.com \
--cc=devicetree@vger.kernel.org \
--cc=javier@osg.samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=t-kristo@ti.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