From: Takashi Iwai <tiwai@suse.de>
To: "Jean-Loïc Charroud" <lagiraudiere+linux@free.fr>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
Stefan Binding <sbinding@opensource.cirrus.com>,
linux-sound <linux-sound@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
patches <patches@opensource.cirrus.com>
Subject: Re: [PATCH v3 0/3] ALSA: hda/realtek: cs35l41: Fix internal speaker support for ASUS UM3402 with missing DSD
Date: Wed, 14 Feb 2024 10:16:43 +0100 [thread overview]
Message-ID: <87h6ibiex0.wl-tiwai@suse.de> (raw)
In-Reply-To: <644212740.650323792.1707867443153.JavaMail.zimbra@free.fr>
On Wed, 14 Feb 2024 00:37:23 +0100,
Jean-Loïc Charroud wrote:
>
> This patch set adds the missing DSD properties, to make the internal speaker works for the "ASUS UM3402" and does some cleanup.
>
> Following feedback, I've divided the initial patch into three independent parts and adjusted the explanations:
> - Patch 1 : Add internal speaker support for ASUS UM3402 with missing DSD
> - Patch 2 : Fix device ID / model name (no functional changes)
> - Patch 3 : Fix order and duplicates entry in quirks table (cleanup, no functional changes)
>
> Thank you Takashi for your guidance
> I hope everything is in good shape now.
Thanks! It's almost fine and I corrected minor things in my side
(e.g. adding Fixes tags), now applied all to for-linus branch.
Takashi
prev parent reply other threads:[~2024-02-14 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 23:37 Jean-Loïc Charroud
2024-02-13 23:38 ` [PATCH v3 1/3] ALSA: hda/realtek: cs35l41: Add " lagiraudiere
2024-02-13 23:42 ` [PATCH v3 2/3] ALSA: hda/realtek: cs35l41: Fix device ID / model name Jean-Loïc Charroud
2024-02-13 23:44 ` [PATCH v3 3/3] ALSA: hda/realtek: cs35l41: Fix order and duplicates in quirks table Jean-Loïc Charroud
2024-02-13 23:51 ` [PATCH v3 2/3] ALSA: hda/realtek: cs35l41: Fix device ID / model name Jean-Loïc Charroud
2024-02-14 9:16 ` Takashi Iwai [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=87h6ibiex0.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=lagiraudiere+linux@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=sbinding@opensource.cirrus.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
all inboxes | Powered by JetHome®