From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v2 2/2] ASoC: atmel-classd: DT binding for PDMIC driver
Date: Tue, 22 Dec 2015 23:49:25 +0000 [thread overview]
Message-ID: <20151222234925.GB16023@sirena.org.uk> (raw)
In-Reply-To: <CAL_JsqKTNJ6Y0OUydkef3aYUO2jzDb30myvGJau-RBoJ3qe8hQ@mail.gmail.com>
On Tue, Dec 22, 2015 at 12:37:24PM -0600, Rob Herring wrote:
> On Sat, Dec 19, 2015 at 5:30 AM, Mark Brown <broonie@kernel.org> wrote:
> >> "label" can be used here if this is really needed.
> > The plastics for the system are often very important for audio
> > configuration - we need userspace to be able to distinguish between
> > systems that are identical even on the electrical level.
> Okay. That is exactly what label is for, so please use it.
Can you send fixes for this please? There's rather a lot of existing
bindings using the current scheme, together with some subsystem code to
help parse them.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20151222/b6671fe3/attachment.sig>
prev parent reply other threads:[~2015-12-22 23:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 9:49 [RESEND PATCH v2 0/2] ASoC: atmel-pdmic: add driver for Atmel PDMIC Songjun Wu
2015-12-17 9:49 ` [RESEND PATCH v2 1/2] ASoC: atmel-pdmic: add the Pulse Density Modulation Interface Controller Songjun Wu
2015-12-17 9:50 ` [RESEND PATCH v2 2/2] ASoC: atmel-classd: DT binding for PDMIC driver Songjun Wu
2015-12-19 4:17 ` Rob Herring
[not found] ` <20151219040913.D0F442C02FD@rob-hp-laptop>
2015-12-19 11:30 ` Mark Brown
2015-12-22 18:37 ` Rob Herring
2015-12-22 23:49 ` Mark Brown [this message]
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=20151222234925.GB16023@sirena.org.uk \
--to=broonie@kernel.org \
--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