From: Mark Brown <broonie@kernel.org>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
alsa-devel@alsa-project.org,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Ben Zhang <benzh@chromium.org>,
Anatol Pomozov <anatol@google.com>,
Grant Likely <grant.likely@linaro.org>,
Bard Liao <bardliao@realtek.com>,
Dylan Reid <dgreid@chromium.org>
Subject: Re: [PATCH 2/2] ASoC: rt5677: Switch to use unified device property API
Date: Tue, 23 Jun 2015 10:46:48 +0100 [thread overview]
Message-ID: <20150623094648.GX14071@sirena.org.uk> (raw)
In-Reply-To: <D1ADF0B6.D4C8F%dvhart@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 563 bytes --]
On Mon, Jun 22, 2015 at 05:05:37PM -0700, Darren Hart wrote:
> On 6/22/15, 3:50 PM, "Mark Brown" <broonie@kernel.org> wrote:
> >Have the Intel audio people been speaking to the UEFI forum about using
> >the new registration process for these properties? More from interest
> >than anything else.
> Yes (although "audio people" is a rather broad term at Intel :-)
It is, as is ACPI people, and these are among the issues here. Is this
stuff going to get used as a trial run of the new process? It'd be good
to know if we should be pushing people towards it.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2015-06-23 9:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 18:12 [PATCH 1/2] ASoC: rt5677: Switch to use descriptor-based gpiod API Ben Zhang
2015-06-22 18:13 ` [PATCH 2/2] ASoC: rt5677: Switch to use unified device property API Ben Zhang
2015-06-22 22:18 ` Pierre-Louis Bossart
2015-06-22 22:50 ` Mark Brown
2015-06-22 23:07 ` Ben Zhang
2015-06-23 0:05 ` Darren Hart
2015-06-23 9:46 ` Mark Brown [this message]
2015-07-07 13:57 ` Applied "ASoC: rt5677: Switch to use unified device property API" to the asoc tree Mark Brown
2015-07-07 13:57 ` Applied "ASoC: rt5677: Switch to use descriptor-based gpiod " 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=20150623094648.GX14071@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=anatol@google.com \
--cc=bardliao@realtek.com \
--cc=benzh@chromium.org \
--cc=dgreid@chromium.org \
--cc=dvhart@linux.intel.com \
--cc=grant.likely@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.com \
--cc=pierre-louis.bossart@linux.intel.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