From: Simon Horman <horms@verge.net.au>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 08/10] ARM: shmobile: armadillo800eva dts: Use generic names for device nodes
Date: Thu, 30 Apr 2015 00:13:34 +0000 [thread overview]
Message-ID: <20150430001333.GC17758@verge.net.au> (raw)
In-Reply-To: <20150430001254.GB17758@verge.net.au>
On Thu, Apr 30, 2015 at 09:12:55AM +0900, Simon Horman wrote:
> On Tue, Apr 28, 2015 at 10:52:37AM +0200, Geert Uytterhoeven wrote:
> > On Mon, Apr 27, 2015 at 3:05 PM, Sergei Shtylyov
> > <sergei.shtylyov@cogentembedded.com> wrote:
> > >> - wm8978: wm8978@1a {
> > >> + wm8978: codec@1a {
> > >
> > > Perhaps sound-codec?
> >
> > Given there's no single instance of "sound-codec" under
> > Documentation/devicetree/, and only four occurrences in DTS files (whoops,
> > I should fix up 3 of them ;-):
>
> :)
>
> I'm happy to help with that if you are dunning short of cycles.
I see you have already sent patches, thanks.
> > arch/arm/boot/dts/r8a7778-bockw.dts: ak4643: sound-codec@12 {
> > arch/arm/boot/dts/r8a7790-lager.dts: ak4643: sound-codec@12 {
> > arch/arm/boot/dts/r8a7791-koelsch.dts: ak4643: sound-codec@12 {
> > arch/xtensa/boot/dts/xtfpga.dtsi: tlv320aic23: sound-codec@0 {
> >
> > I'm strongly leaning towards "codec".
>
> On the strength of that I have queued this up.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2015-04-30 0:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 12:55 [PATCH 00/10] ARM: shmobile: Use generic names for device nodes Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 01/10] ARM: shmobile: r8a7740 dtsi: " Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 02/10] ARM: shmobile: r8a7778 " Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 03/10] ARM: shmobile: r8a7779 " Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 04/10] ARM: shmobile: r8a7790 " Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 05/10] ARM: shmobile: r8a7791 " Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 06/10] ARM: shmobile: sh73a0 " Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 07/10] ARM: shmobile: ape6evm dts: " Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 08/10] ARM: shmobile: armadillo800eva " Geert Uytterhoeven
2015-04-27 13:05 ` Sergei Shtylyov
2015-04-28 8:52 ` Geert Uytterhoeven
2015-04-30 0:12 ` Simon Horman
2015-04-30 0:13 ` Simon Horman [this message]
2015-04-27 12:55 ` [PATCH 09/10] ARM: shmobile: kzm9d " Geert Uytterhoeven
2015-04-27 12:55 ` [PATCH 10/10] ARM: shmobile: marzen " Geert Uytterhoeven
2015-04-27 13:06 ` Sergei Shtylyov
2015-04-27 13:53 ` Geert Uytterhoeven
2015-04-28 0:57 ` [PATCH 00/10] ARM: shmobile: " 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=20150430001333.GC17758@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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