From: Takashi Iwai <tiwai@suse.de>
To: Cem Kaya <cemkaya.boun@gmail.com>
Cc: "tiwai@suse.com" <tiwai@suse.com>,
"mario.limonciello@amd.com" <mario.limonciello@amd.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] Add Dell G15 5525 Ryzen Edition to quirks list for acp6x so that internal DMIC works.
Date: Mon, 10 Apr 2023 18:39:14 +0200 [thread overview]
Message-ID: <878rez4rpp.wl-tiwai@suse.de> (raw)
In-Reply-To: <38108AA1-01F5-4C48-A03E-73E9CAC3E8CF@getmailspring.com>
On Mon, 10 Apr 2023 18:03:36 +0200,
Cem Kaya wrote:
>
>
> From 972ad712cfda9453a720b73c645601db23d708c6 Mon Sep 17 00:00:00 2001
> From: Cem Kaya <cemkaya.boun@gmail.com>
> Date: Sat, 8 Apr 2023 16:20:42 +0200
> Subject: [PATCH v3] Add Dell G15 5525 Ryzen Edition to quirks list for acp6x
> so
> that internal DMIC works.
> Signed-off-by: Cem Kaya <cemkaya.boun@gmail.com>
> Commit: Add Dell G15 5525 Ryzen Edition to quirks list for acp6x so that
> internal mic works.
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217155
Looks better, but still a few things to be correctly formatted.
The subject line needs the proper prefix, depending on the subsystem.
In your case, put "ASoC: amd:", for example. Also, the subject line
should be concise.
The patch description is no such a tag like "Commit:", but it should
be filled in the commit log. This can be as long as you like, but put
the line breaks appropriately.
The Link and Signed-off-by tags follow after the patch description
with a blank line.
In your case, it'd be worth to put Cc-to-stable, too.
So, it should be like:
-- 8< --
From: Cem Kaya <cemkaya.boun@gmail.com>
Subject: [PATCH v3] ASoC: amd: Add Dell G15 5525 to quirks list for internal DMIC
Add Dell G15 5525 Ryzen Edition to quirks list for acp6x so that
internal mic works.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=217155
Cc: <stable@vger.kernel.org>
Signed-off-by: Cem Kaya <cemkaya.boun@gmail.com>
-- 8< --
..., and get the right maintainer via scripts/get_maintainer.pl, put
them to Cc.
For details, please read
Documentation/process/submitting-patches.rst.
*HOWEVER*: the most serious problem is in this patch submission is...
> @@ -45,6 +45,13 @@ static struct snd_soc_card acp6x_card = {
> };
>
> static const struct dmi_system_id yc_acp_quirk_table[] = {
> + {
> + .driver_data = &acp6x_card,
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "Dell Inc."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "Dell G15 5525"),
> + }
> + },
... somehow the patch itself became broken (while v2 patch looked
OK). Please verify how this got broken and try to submit correctly at
the next time.
thanks,
Takashi
WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: Cem Kaya <cemkaya.boun@gmail.com>
Cc: "perex@perex.cz" <perex@perex.cz>,
"tiwai@suse.com" <tiwai@suse.com>,
"mario.limonciello@amd.com" <mario.limonciello@amd.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] Add Dell G15 5525 Ryzen Edition to quirks list for acp6x so that internal DMIC works.
Date: Mon, 10 Apr 2023 18:39:14 +0200 [thread overview]
Message-ID: <878rez4rpp.wl-tiwai@suse.de> (raw)
In-Reply-To: <38108AA1-01F5-4C48-A03E-73E9CAC3E8CF@getmailspring.com>
On Mon, 10 Apr 2023 18:03:36 +0200,
Cem Kaya wrote:
>
>
> From 972ad712cfda9453a720b73c645601db23d708c6 Mon Sep 17 00:00:00 2001
> From: Cem Kaya <cemkaya.boun@gmail.com>
> Date: Sat, 8 Apr 2023 16:20:42 +0200
> Subject: [PATCH v3] Add Dell G15 5525 Ryzen Edition to quirks list for acp6x
> so
> that internal DMIC works.
> Signed-off-by: Cem Kaya <cemkaya.boun@gmail.com>
> Commit: Add Dell G15 5525 Ryzen Edition to quirks list for acp6x so that
> internal mic works.
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217155
Looks better, but still a few things to be correctly formatted.
The subject line needs the proper prefix, depending on the subsystem.
In your case, put "ASoC: amd:", for example. Also, the subject line
should be concise.
The patch description is no such a tag like "Commit:", but it should
be filled in the commit log. This can be as long as you like, but put
the line breaks appropriately.
The Link and Signed-off-by tags follow after the patch description
with a blank line.
In your case, it'd be worth to put Cc-to-stable, too.
So, it should be like:
-- 8< --
From: Cem Kaya <cemkaya.boun@gmail.com>
Subject: [PATCH v3] ASoC: amd: Add Dell G15 5525 to quirks list for internal DMIC
Add Dell G15 5525 Ryzen Edition to quirks list for acp6x so that
internal mic works.
Link: https://bugzilla.kernel.org/show_bug.cgi?id=217155
Cc: <stable@vger.kernel.org>
Signed-off-by: Cem Kaya <cemkaya.boun@gmail.com>
-- 8< --
..., and get the right maintainer via scripts/get_maintainer.pl, put
them to Cc.
For details, please read
Documentation/process/submitting-patches.rst.
*HOWEVER*: the most serious problem is in this patch submission is...
> @@ -45,6 +45,13 @@ static struct snd_soc_card acp6x_card = {
> };
>
> static const struct dmi_system_id yc_acp_quirk_table[] = {
> + {
> + .driver_data = &acp6x_card,
> + .matches = {
> + DMI_MATCH(DMI_BOARD_VENDOR, "Dell Inc."),
> + DMI_MATCH(DMI_PRODUCT_NAME, "Dell G15 5525"),
> + }
> + },
... somehow the patch itself became broken (while v2 patch looked
OK). Please verify how this got broken and try to submit correctly at
the next time.
thanks,
Takashi
next prev parent reply other threads:[~2023-04-10 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 16:03 [PATCH v3] Add Dell G15 5525 Ryzen Edition to quirks list for acp6x so that internal DMIC works Cem Kaya
2023-04-10 16:39 ` Takashi Iwai [this message]
2023-04-10 16:39 ` Takashi Iwai
2023-04-10 16:44 ` Takashi Iwai
2023-04-10 16:44 ` 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=878rez4rpp.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=cemkaya.boun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mario.limonciello@amd.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 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.