From: Mark Brown <broonie@kernel.org>
To: Biju Das <biju.das@bp.renesas.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Simon Horman <horms@verge.net.au>,
Magnus Damm <magnus.damm@gmail.com>,
Chris Paterson <chris.paterson2@renesas.com>,
Fabrizio Castro <fabrizio.castro@bp.renesas.com>,
alsa-devel@alsa-project.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: ASoC: rsnd: Add device tree support for r8a774[35]
Date: Wed, 13 Dec 2017 12:20:52 +0000 [thread overview]
Message-ID: <20171213122052.GG6416@sirena.org.uk> (raw)
In-Reply-To: <1513102155-47925-1-git-send-email-biju.das@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
On Tue, Dec 12, 2017 at 06:09:15PM +0000, Biju Das wrote:
> Document r8a774[35] specific compatible strings. The Renesas RZ/G1[ME]
> (r8a774[35]) sound modules are identical to the R-Car Gen2 family.
> No driver change is needed as the fallback compatible string
> "renesas,rcar_sound-gen2" activates the right code in the driver.
Please submit patches using subject lines reflecting the style for the
subsystem. This makes it easier for people to identify relevant
patches. Look at what existing commits in the area you're changing are
doing and make sure your subject lines visually resemble what they're
doing.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-12-13 12:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 18:09 [PATCH] dt-bindings: ASoC: rsnd: Add device tree support for r8a774[35] Biju Das
2017-12-13 10:16 ` Geert Uytterhoeven
2017-12-13 12:20 ` Mark Brown [this message]
2017-12-13 12:34 ` Geert Uytterhoeven
2017-12-13 12:55 ` Mark Brown
2017-12-13 13:14 ` Biju Das
2017-12-13 13:35 ` [PATCH v2] " Biju Das
2017-12-13 13:45 ` Geert Uytterhoeven
2017-12-13 15:46 ` Applied "ASoC: rsnd: Add device tree support for r8a774[35]" to the asoc tree Mark Brown
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=20171213122052.GG6416@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=biju.das@bp.renesas.com \
--cc=chris.paterson2@renesas.com \
--cc=fabrizio.castro@bp.renesas.com \
--cc=horms@verge.net.au \
--cc=lgirdwood@gmail.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--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