From: Mark Brown <broonie@kernel.org>
To: Dylan Reid <dgreid@chromium.org>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, lars@metafoo.de,
lgirdwood@gmail.com, zhengxing@rock-chips.com
Subject: Re: [RFC 1/5] ALSA: Add jack types to dt-bindings
Date: Mon, 25 May 2015 13:11:54 +0100 [thread overview]
Message-ID: <20150525121154.GK21391@sirena.org.uk> (raw)
In-Reply-To: <1432332563-15447-2-git-send-email-dgreid@chromium.org>
[-- Attachment #1.1: Type: text/plain, Size: 232 bytes --]
On Fri, May 22, 2015 at 03:09:19PM -0700, Dylan Reid wrote:
> Adding the jack type to the dt-bindings directory will allow for device
> tree files to specify the type of audio jacks that are present for a
> board.
Applied, thanks.
[-- 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-05-25 13:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 22:09 [RFC 0/5] Add a gpio jack device Dylan Reid
2015-05-22 22:09 ` [RFC 1/5] ALSA: Add jack types to dt-bindings Dylan Reid
2015-05-25 12:11 ` Mark Brown [this message]
2015-05-22 22:09 ` [RFC 2/5] ASoC: jack - add_gpiods accepts filled descriptors Dylan Reid
2015-05-25 12:12 ` Mark Brown
2015-05-22 22:09 ` [RFC 3/5] ASoC: Add GPIO based jack device Dylan Reid
2015-05-25 12:11 ` Mark Brown
2015-05-26 6:20 ` Dylan Reid
2015-05-22 22:09 ` [RFC 4/5] ASoC: tegra_max98090: Change nyan to use gpio-jack Dylan Reid
2015-05-22 22:09 ` [RFC 5/5] ARM: tegra: nyan: specify gpio-audio-jack device Dylan Reid
2015-05-25 15:17 ` [RFC 0/5] Add a gpio jack device Lars-Peter Clausen
2015-05-25 17:15 ` Mark Brown
2015-05-25 18:58 ` Dylan Reid
2015-05-26 18:43 ` Lars-Peter Clausen
2015-05-26 20:14 ` Mark Brown
2015-05-27 4:22 ` Dylan Reid
2015-05-27 11:15 ` Lars-Peter Clausen
2015-05-27 17:26 ` Mark Brown
2015-05-28 5:38 ` Dylan Reid
2015-05-28 10:17 ` Mark Brown
2015-05-27 11:12 ` Lars-Peter Clausen
2015-05-28 19:35 ` 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=20150525121154.GK21391@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=dgreid@chromium.org \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=tiwai@suse.de \
--cc=zhengxing@rock-chips.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