From: Mark Brown <broonie@kernel.org>
To: Benson Leung <bleung@chromium.org>
Cc: linux-kernel@vger.kernel.org, harshapriya.n@intel.com,
naveen.m@intel.com, srinivas.kandagatla@linaro.org,
cychiang@chromium.org, dgreid@chromium.org,
anatol.pomozov@gmail.com, bleung@google.com
Subject: Re: [PATCH 0/5] ASoC: Map BTN_0 for Android Headsets to KEY_PLAYPAUSE
Date: Mon, 27 Nov 2017 13:04:00 +0000 [thread overview]
Message-ID: <20171127130400.72ddqdndv3blcck6@sirena.org.uk> (raw)
In-Reply-To: <20171122205643.99783-1-bleung@chromium.org>
[-- Attachment #1: Type: text/plain, Size: 578 bytes --]
On Wed, Nov 22, 2017 at 12:56:38PM -0800, Benson Leung wrote:
> The Android 3.5mm Headset jack specification mentions that BTN_0 should
> be mapped to KEY_MEDIA, but this is less logical than KEY_PLAYPAUSE,
> which has much broader userspace support.
You need to send patches to the relevant mailing lists, this provides an
archive of the review that happens and allows people other than the
reviewers you name to look at the patches. Please see SubmittingPatches
for details of the patch submission process.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2017-11-27 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 20:56 Benson Leung
2017-11-22 20:56 ` [PATCH 1/5] ASoC: Intel: kbl_rt5663_rt5514_max98927: Map BTN_0 " Benson Leung
2017-11-22 20:56 ` [PATCH 2/5] ASoC: Intel: kbl_rt5663_max98927: " Benson Leung
2017-11-22 20:56 ` [PATCH 3/5] ASoC: ts3a227e: " Benson Leung
2017-11-22 20:56 ` [PATCH 4/5] ASoC: rk3399_gru_sound: " Benson Leung
2017-11-22 20:56 ` [PATCH 5/5] ASoC: qcom: apq8016-sbc: " Benson Leung
2017-11-27 13:04 ` 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=20171127130400.72ddqdndv3blcck6@sirena.org.uk \
--to=broonie@kernel.org \
--cc=anatol.pomozov@gmail.com \
--cc=bleung@chromium.org \
--cc=bleung@google.com \
--cc=cychiang@chromium.org \
--cc=dgreid@chromium.org \
--cc=harshapriya.n@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naveen.m@intel.com \
--cc=srinivas.kandagatla@linaro.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
all inboxes | Powered by JetHome®