From: Greg KH <greg@kroah.com>
To: Hui Wang <hui.wang@canonical.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org, stable@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda - Adding a group of pin definition to fix headset problem
Date: Thu, 23 Mar 2017 07:10:53 +0100 [thread overview]
Message-ID: <20170323061053.GA21389@kroah.com> (raw)
In-Reply-To: <1490234425-32189-1-git-send-email-hui.wang@canonical.com>
On Thu, Mar 23, 2017 at 10:00:25AM +0800, Hui Wang wrote:
> A new Dell laptop needs to apply ALC269_FIXUP_DELL1_MIC_NO_PRESENCE to
> fix the headset problem, and the pin definiton of this machine is not
> in the pin quirk table yet, now adding it to the table.
>
> Signed-off-by: Hui Wang <hui.wang@canonical.com>
> ---
> sound/pci/hda/patch_realtek.c | 2 ++
> 1 file changed, 2 insertions(+)
<formletter>
This is not the correct way to submit patches for inclusion in the
stable kernel tree. Please read Documentation/stable_kernel_rules.txt
for how to do this properly.
</formletter>
prev parent reply other threads:[~2017-03-23 7:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 2:00 [PATCH] ALSA: hda - Adding a group of pin definition to fix headset problem Hui Wang
2017-03-23 6:10 ` Greg KH [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=20170323061053.GA21389@kroah.com \
--to=greg@kroah.com \
--cc=alsa-devel@alsa-project.org \
--cc=hui.wang@canonical.com \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.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;
as well as URLs for NNTP newsgroup(s).