From: Geraldo Nascimento <geraldogabriel@gmail.com>
To: marcel <marcelg@gmx.com>
Cc: linux-sound@vger.kernel.org
Subject: Re: [PATCH] Add Asus VivoBook S 16X to quirks table for acp6x
Date: Mon, 5 Feb 2024 23:37:12 -0300 [thread overview]
Message-ID: <ZcGbWHRJ9ewRvAa7@geday> (raw)
In-Reply-To: <655fb630-e5a8-4993-8706-085476c7fe2f@gmx.com>
On Mon, Feb 05, 2024 at 11:48:31AM +0800, marcel wrote:
> This patch enables microphone driver on Asus Vivobook S 16X laptop by
> adding it to quirks table.
>
> Signed-off-by: Marcel Geraltowski <marcelg@gmx.com>
Hi Marcel, thanks for the patch.
Remember to add the correct subsystem and driver name just after the
[PATCH v?] subject. While the change in and of itself is OK, you sorted
it, etc., your MUA ate the tab characters and replaced it with spaces.
This is a big no-no.
Also remember to add the maintainers to the Cc:, in this case Jaroslav
Kysela and Takashi Iwai. Failure to do that may result in unnoticed and
thus missing patches.
Thank you,
Geraldo Nascimento
>
> - - -
>
> --- sound/sound/soc/amd/yc/acp6x-mach.c.orig 2024-02-05
> 10:26:11.123897233 +0800
> +++ sound/sound/soc/amd/yc/acp6x-mach.c 2024-02-05 11:04:40.554566909
> +0800
> @@ -262,6 +262,13 @@ static const struct dmi_system_id yc_acp
> DMI_MATCH(DMI_PRODUCT_NAME, "M5402RA"),
> }
> },
> + {
> + .driver_data = &acp6x_card,
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK COMPUTER
> INC."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "M5602RA"),
> + }
> + },
> {
> .driver_data = &acp6x_card,
> .matches = {
>
next prev parent reply other threads:[~2024-02-06 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 3:48 [PATCH] Add Asus VivoBook S 16X to quirks table for acp6x marcel
2024-02-06 2:37 ` Geraldo Nascimento [this message]
[not found] ` <1b37b9ee-68db-425c-b878-71847459fb3c@gmx.com>
[not found] ` <7bbc4afe-30de-4342-953d-2cddcb3c7933@gmx.com>
2024-03-20 3:40 ` Geraldo Nascimento
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=ZcGbWHRJ9ewRvAa7@geday \
--to=geraldogabriel@gmail.com \
--cc=linux-sound@vger.kernel.org \
--cc=marcelg@gmx.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.