From: Justin Monk <jmonk86@gmail.com>
To: alsa-devel@alsa-project.org, superquad.vortex2@gmail.com
Subject: Re: [PATCH v2- ALSA 2/3] HDA - create headset mic jack which use headphone pin sense
Date: Tue, 5 Apr 2016 13:15:08 +0300 [thread overview]
Message-ID: <CALivufeCutVbhC7iQ5VGPpjm3Nds3YejzcKsm2NDFRsObi+nSA@mail.gmail.com> (raw)
Team,
I was wondering when this patch would be available, I figured it would
already be in the down stream. If not I would love to test it. I have
minimal programming skills but would love to help.
Kernel Bug Tracker – Bug 107851
4.2.0-18-generic
currently running
4.4.6-300.fc23.x86_64
Thanks,
Justin Monk
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2016-04-05 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 10:15 Justin Monk [this message]
2016-04-05 14:35 ` [PATCH v2- ALSA 2/3] HDA - create headset mic jack which use headphone pin sense Raymond Yau
-- strict thread matches above, loose matches on Subject: below --
2015-09-23 2:40 Raymond Yau
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=CALivufeCutVbhC7iQ5VGPpjm3Nds3YejzcKsm2NDFRsObi+nSA@mail.gmail.com \
--to=jmonk86@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=superquad.vortex2@gmail.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;
as well as URLs for NNTP newsgroup(s).