From: Takashi Iwai <tiwai@suse.de>
To: Meng Tang <tangmeng@uniontech.com>
Cc: perex@perex.cz, tiwai@suse.com, tcrawford@system76.com,
kai.heng.feng@canonical.com, tanureal@opensource.cirrus.com,
cam@neo-zeon.de, kailang@realtek.com,
sbinding@opensource.cirrus.com, andy.chi@canonical.com,
yong.wu@mediatek.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ALSA: hda - Add fixup for Dell Latitidue E5430
Date: Tue, 12 Jul 2022 11:14:22 +0200 [thread overview]
Message-ID: <87lesyr8up.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220712060005.20176-1-tangmeng@uniontech.com>
On Tue, 12 Jul 2022 08:00:05 +0200,
Meng Tang wrote:
>
> Another Dell model, another fixup entry: Latitude E5430 needs the same
> fixup as other Latitude E series as workaround for noise problems.
>
> Signed-off-by: Meng Tang <tangmeng@uniontech.com>
Thanks, applied now.
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Meng Tang <tangmeng@uniontech.com>
Cc: sbinding@opensource.cirrus.com, kailang@realtek.com,
linux-kernel@vger.kernel.org, tanureal@opensource.cirrus.com,
tcrawford@system76.com, tiwai@suse.com,
kai.heng.feng@canonical.com, andy.chi@canonical.com,
cam@neo-zeon.de, alsa-devel@alsa-project.org,
yong.wu@mediatek.com
Subject: Re: [PATCH] ALSA: hda - Add fixup for Dell Latitidue E5430
Date: Tue, 12 Jul 2022 11:14:22 +0200 [thread overview]
Message-ID: <87lesyr8up.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220712060005.20176-1-tangmeng@uniontech.com>
On Tue, 12 Jul 2022 08:00:05 +0200,
Meng Tang wrote:
>
> Another Dell model, another fixup entry: Latitude E5430 needs the same
> fixup as other Latitude E series as workaround for noise problems.
>
> Signed-off-by: Meng Tang <tangmeng@uniontech.com>
Thanks, applied now.
Takashi
next prev parent reply other threads:[~2022-07-12 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 6:00 [PATCH] ALSA: hda - Add fixup for Dell Latitidue E5430 Meng Tang
2022-07-12 6:00 ` Meng Tang
2022-07-12 9:14 ` Takashi Iwai [this message]
2022-07-12 9:14 ` Takashi Iwai
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=87lesyr8up.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=andy.chi@canonical.com \
--cc=cam@neo-zeon.de \
--cc=kai.heng.feng@canonical.com \
--cc=kailang@realtek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=sbinding@opensource.cirrus.com \
--cc=tangmeng@uniontech.com \
--cc=tanureal@opensource.cirrus.com \
--cc=tcrawford@system76.com \
--cc=tiwai@suse.com \
--cc=yong.wu@mediatek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.