From: Simon Horman <horms@verge.net.au>
To: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
Cc: magnus.damm@gmail.com, robh+dt@kernel.org, mark.rutland@arm.com,
catalin.marinas@arm.com, will.deacon@arm.com,
linux-renesas-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
chris.paterson2@renesas.com, geert+renesas@glider.be
Subject: Re: [PATCH] arm64: dts: r8a7795: Add DRIF support
Date: Fri, 23 Jun 2017 11:41:04 +0200 [thread overview]
Message-ID: <20170623094104.GA24191@verge.net.au> (raw)
In-Reply-To: <20170623091320.12664-1-ramesh.shanmugasundaram@bp.renesas.com>
On Fri, Jun 23, 2017 at 10:13:20AM +0100, Ramesh Shanmugasundaram wrote:
> Adds the DRIF controller nodes for r8a7795.
>
> Signed-off-by: Ramesh Shanmugasundaram <ramesh.shanmugasundaram@bp.renesas.com>
> ---
> Hi Simon,
>
> This patch is based on renesas-devel-20170622-v4.12-rc6 tag.
> It is verified on both H3 ES1.1 and ES2.0 SoC revisions.
>
> The bindings[1] and the driver[2] were pushed into the media_tree.
>
> [1] https://git.linuxtv.org/media_tree.git/commit/?id=54a707ea011601f06cc5ef7fe6d0daac71ab0622
> [2] https://git.linuxtv.org/media_tree.git/commit/?id=7625ee981af166ddb569e2e6c0006e2af471326f
>
Thanks. Has this been tested not to cause regressions when
applied on top of renesas-devel-20170622-v4.12-rc6 (without the driver
changes) ?
next prev parent reply other threads:[~2017-06-23 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 9:13 [PATCH] arm64: dts: r8a7795: Add DRIF support Ramesh Shanmugasundaram
2017-06-23 9:41 ` Simon Horman [this message]
2017-06-23 10:37 ` Ramesh Shanmugasundaram
[not found] ` <20170623091320.12664-1-ramesh.shanmugasundaram-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-07-03 9:03 ` Simon Horman
2017-07-05 9:41 ` Geert Uytterhoeven
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=20170623094104.GA24191@verge.net.au \
--to=horms@verge.net.au \
--cc=catalin.marinas@arm.com \
--cc=chris.paterson2@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=ramesh.shanmugasundaram@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.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).