From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: "dt list" <devicetree@vger.kernel.org>,
linux-omap <linux-omap@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Benoît Cousson" <bcousson@baylibre.com>
Subject: Re: [PATCH V2] ARM: dts: OMAP5: Add device nodes for ABB
Date: Tue, 8 Jul 2014 01:13:28 -0700 [thread overview]
Message-ID: <20140708081327.GB28884@atomide.com> (raw)
In-Reply-To: <CAGo_u6peyH=VScObgLJxX5kS2J77y5WMsE0O71W4GPDpKaMV=g@mail.gmail.com>
* Nishanth Menon <nm@ti.com> [140707 07:25]:
> On Mon, Jul 7, 2014 at 6:32 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * Nishanth Menon <nm@ti.com> [140605 18:12]:
> >> From: "Andrii.Tseglytskyi" <andrii.tseglytskyi@ti.com>
> >>
> >> Add ABB device nodes for OMAP5 family of devices. Data is based on
> >> final production OMAP543x Technical Reference Manual revision Z (April 2013).
> >> Final production Data Manual for OMAP5432 SWPS050F(APRIL 2014).
> >>
> >> [nm@ti.com: co-developer and updates to latest documentation]
> >> Signed-off-by: Nishanth Menon <nm@ti.com>
> >> Signed-off-by: Andrii.Tseglytskyi <andrii.tseglytskyi@ti.com>
> >> ---
> >> Original patch (v1): https://patchwork.kernel.org/patch/3555191/
> >>
> >> Rest of the series was accepted, however, I had to drop this
> >> previously to ensure that the data we introduce is compatible with
> >> production samples and existing pre-production samples on various
> >> OMAP5uEVMs already in circulation.
> >
> > Is this OK to queue for v3.17 or do we need it for the -rc cycle?
> >
>
> .17 should be fine Tony. Thanks for following up.
OK applying into omap-for-v3.17/fixes-not-urgent thanks.
Tony
prev parent reply other threads:[~2014-07-08 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 1:11 [PATCH V2] ARM: dts: OMAP5: Add device nodes for ABB Nishanth Menon
2014-07-07 11:32 ` Tony Lindgren
2014-07-07 14:23 ` Nishanth Menon
2014-07-08 8:13 ` 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=20140708081327.GB28884@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@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;
as well as URLs for NNTP newsgroup(s).