From: Stephen Warren <swarren@wwwdotorg.org>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>, linux-kernel@vger.kernel.org
Cc: Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Alexandre Courbot <gnurou@gmail.com>,
alsa-devel@alsa-project.org, devicetree@vger.kernel.org,
Dylan Reid <dgreid@chromium.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Jaroslav Kysela <perex@perex.cz>,
Kumar Gala <galak@codeaurora.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-tegra@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>, Rob Herring <robh+dt@kernel.org>,
Takashi Iwai <tiwai@suse.de>,
Thierry Reding <thierry.reding@gmail.com>,
Wolfram Sang <wsa@the-dreams.de>
Subject: Re: [PATCH 0/3] Expose more controls from tegra-max98090
Date: Wed, 11 Feb 2015 09:34:28 -0700 [thread overview]
Message-ID: <54DB8494.6040600@wwwdotorg.org> (raw)
In-Reply-To: <1423666200-32365-1-git-send-email-tomeu.vizoso@collabora.com>
On 02/11/2015 07:49 AM, Tomeu Vizoso wrote:
> Hello,
>
> we need some more controls in userspace so policy can be applied at events
> such as microphone and headphone jacks being plugged in, to be used by
> Tegra-based Chromebooks.
The series,
Acked-by: Stephen Warren <swarren@nvidia.com>
next prev parent reply other threads:[~2015-02-11 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 14:49 [PATCH 0/3] Expose more controls from tegra-max98090 Tomeu Vizoso
2015-02-11 14:49 ` [PATCH 1/3] ASoC: tegra: Expose Headphones pin to userspace Tomeu Vizoso
2015-02-11 14:49 ` [PATCH 2/3] ASoC: tegra: Add sink for the internal mic to tegra_max98090 Tomeu Vizoso
2015-02-11 14:49 ` [PATCH 3/3] ASoC: tegra: Add control for the Mic Jack pin Tomeu Vizoso
2015-02-11 16:34 ` Stephen Warren [this message]
2015-02-21 14:50 ` [PATCH 0/3] Expose more controls from tegra-max98090 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=54DB8494.6040600@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dgreid@chromium.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=javier.martinez@collabora.co.uk \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=perex@perex.cz \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.de \
--cc=tomeu.vizoso@collabora.com \
--cc=wsa@the-dreams.de \
/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