From: Simon Horman <horms@verge.net.au>
To: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Niklas Söderlund" <niklas.soderlund@ragnatech.se>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
devicetree@vger.kernel.org,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Chris Paterson" <Chris.Paterson2@renesas.com>,
"Biju Das" <biju.das@bp.renesas.com>
Subject: Re: [PATCH v2 2/4] dt-bindings: media: rcar_vin: add device tree support for r8a774[35]
Date: Fri, 17 Nov 2017 07:35:52 -0800 [thread overview]
Message-ID: <20171117153551.xdnr74k7az4f76vf@verge.net.au> (raw)
In-Reply-To: <1510856571-30281-3-git-send-email-fabrizio.castro@bp.renesas.com>
On Thu, Nov 16, 2017 at 06:22:49PM +0000, Fabrizio Castro wrote:
> Add compatible strings for r8a7743 and r8a7745. No driver change
> is needed as "renesas,rcar-gen2-vin" will activate the right code.
> However, it is good practice to document compatible strings for the
> specific SoC as this allows SoC specific changes to the driver if
> needed, in addition to document SoC support and therefore allow
> checkpatch.pl to validate compatible string values.
>
> Signed-off-by: Fabrizio Castro <fabrizio.castro@bp.renesas.com>
> Reviewed-by: Biju Das <biju.das@bp.renesas.com>
Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
next prev parent reply other threads:[~2017-11-17 15:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 18:22 [PATCH v2 0/4] Add VIN support to r8a774[35] Fabrizio Castro
2017-11-16 18:22 ` [PATCH v2 1/4] dt-bindings: media: rcar_vin: Reverse SoC part number list Fabrizio Castro
2017-11-17 20:31 ` Rob Herring
2017-11-23 9:28 ` Geert Uytterhoeven
[not found] ` <1510856571-30281-2-git-send-email-fabrizio.castro-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-11-17 15:35 ` Simon Horman
2017-11-20 10:19 ` Simon Horman
2017-11-28 13:34 ` Niklas Söderlund
2018-01-24 17:02 ` Fabrizio Castro
[not found] ` <1510856571-30281-1-git-send-email-fabrizio.castro-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-11-16 18:22 ` [PATCH v2 2/4] dt-bindings: media: rcar_vin: add device tree support for r8a774[35] Fabrizio Castro
2017-11-17 15:35 ` Simon Horman [this message]
2017-11-17 20:32 ` Rob Herring
2017-11-22 12:53 ` Geert Uytterhoeven
2017-11-28 13:35 ` Niklas Söderlund
2017-12-19 10:20 ` Fabrizio Castro
[not found] ` <1510856571-30281-3-git-send-email-fabrizio.castro-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2018-01-24 17:05 ` Fabrizio Castro
2017-11-16 18:22 ` [PATCH v2 3/4] ARM: dts: r8a7743: add VIN dt support Fabrizio Castro
2017-11-20 10:22 ` Simon Horman
2017-11-16 18:22 ` [PATCH v2 4/4] ARM: dts: r8a7745: " Fabrizio Castro
[not found] ` <1510856571-30281-5-git-send-email-fabrizio.castro-kTT6dE0pTRh9uiUsa/gSgQ@public.gmane.org>
2017-11-20 10:22 ` Simon Horman
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=20171117153551.xdnr74k7az4f76vf@verge.net.au \
--to=horms@verge.net.au \
--cc=Chris.Paterson2@renesas.com \
--cc=biju.das@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=fabrizio.castro@bp.renesas.com \
--cc=geert@linux-m68k.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=robh+dt@kernel.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).