From: Tony Lindgren <tony@atomide.com>
To: Benoit Parrot <bparrot@ti.com>
Cc: Tero Kristo <t-kristo@ti.com>, Rob Herring <robh+dt@kernel.org>,
linux-omap@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Patch 0/3] ARM: dts: dra7: add vpe nodes
Date: Tue, 22 Oct 2019 09:30:48 -0700 [thread overview]
Message-ID: <20191022163048.GY5610@atomide.com> (raw)
In-Reply-To: <20191022162720.yile7i4qwxgbuuou@ti.com>
* Benoit Parrot <bparrot@ti.com> [191022 16:28]:
> Tony,
>
> Ping,
>
> I already had comments from Rob but i would like your feedback before
> sending a v2.
Looks good to me in general other than what Rob commented
on. Did not spot any node naming issues here :)
Regards,
Tony
next prev parent reply other threads:[~2019-10-22 16:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 17:56 [Patch 0/3] ARM: dts: dra7: add vpe nodes Benoit Parrot
2019-10-09 17:56 ` Benoit Parrot
2019-10-09 17:56 ` [Patch 1/3] dt-bindings: media: ti-vpe: Document VPE driver Benoit Parrot
2019-10-09 17:56 ` Benoit Parrot
2019-10-15 22:29 ` Rob Herring
2019-10-16 13:22 ` Benoit Parrot
2019-10-16 13:22 ` Benoit Parrot
2019-10-16 15:36 ` Rob Herring
2019-10-09 17:56 ` [Patch 2/3] ARM: dts: dra7: add vpe clkctrl node Benoit Parrot
2019-10-09 17:56 ` Benoit Parrot
2019-10-09 17:56 ` [Patch 3/3] ARM: dts: dra7: Add ti-sysc node for VPE Benoit Parrot
2019-10-09 17:56 ` Benoit Parrot
2019-10-22 16:27 ` [Patch 0/3] ARM: dts: dra7: add vpe nodes Benoit Parrot
2019-10-22 16:27 ` Benoit Parrot
2019-10-22 16:30 ` Tony Lindgren [this message]
2019-10-22 16:33 ` Benoit Parrot
2019-10-22 16:33 ` Benoit Parrot
2019-10-22 16:37 ` Tony Lindgren
2019-10-22 16:44 ` Benoit Parrot
2019-10-22 16:44 ` Benoit Parrot
2019-10-22 16:46 ` Tony Lindgren
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=20191022163048.GY5610@atomide.com \
--to=tony@atomide.com \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.