From: Takashi Iwai <tiwai@suse.de>
To: Huacai Chen <chenhc@lemote.com>
Cc: Huacai Chen <chenhuacai@gmail.com>,
alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.com>
Subject: Re: [PATCH] ALSA: hda/realtek: Add alc269/alc662 pin-tables for Loongson-3 laptops
Date: Sun, 02 Aug 2020 11:48:55 +0200 [thread overview]
Message-ID: <s5hy2mx74zc.wl-tiwai@suse.de> (raw)
In-Reply-To: <1596360400-32425-1-git-send-email-chenhc@lemote.com>
On Sun, 02 Aug 2020 11:26:40 +0200,
Huacai Chen wrote:
>
> There are several Loongson-3 based laptops produced by CZC or Lemote,
> they use alc269/alc662 codecs and need specific pin-tables, this patch
> add their pin-tables.
>
> Signed-off-by: Huacai Chen <chenhc@lemote.com>
Thanks, applied now with a minor correction of coding style.
At the next time, please try to run scripts/checkpatch.pl once.
Takashi
next prev parent reply other threads:[~2020-08-02 9:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 9:26 [PATCH] ALSA: hda/realtek: Add alc269/alc662 pin-tables for Loongson-3 laptops Huacai Chen
2020-08-02 9:48 ` Takashi Iwai [this message]
2020-08-02 10:07 ` Huacai Chen
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=s5hy2mx74zc.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=chenhc@lemote.com \
--cc=chenhuacai@gmail.com \
--cc=tiwai@suse.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).