From: Takashi Iwai <tiwai@suse.de>
To: Sharwesh05 <sharweshraajan@gmail.com>
Cc: tiwai@suse.com, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modified: sound/pci/hda/patch_realtek.c
Date: Wed, 26 Mar 2025 08:26:55 +0100 [thread overview]
Message-ID: <87cye4b6bk.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250325150510.31452-1-sharweshraajan@gmail.com>
On Tue, 25 Mar 2025 16:05:10 +0100,
Sharwesh05 wrote:
>
Thanks for the patch.
But, please make the patch in a proper format, namely, have the
appropriate Subject line starting with the prefix "ALSA: hda/realtek:"
and containing the concise description about the patch. Then put more
information about the changes (why it's needed and what it fixes /
changes) in the patch description, followed by a blank line, and most
importantly, your Signed-off-by tag with your real name and address;
it's a legal requirement.
Please check Documentation/admin/submitting-patches.rst for details.
About the code change:
> ---
> sound/pci/hda/patch_realtek.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
> index a84857a3c2bf..8c2375476952 100644
> --- a/sound/pci/hda/patch_realtek.c
> +++ b/sound/pci/hda/patch_realtek.c
> @@ -4739,6 +4739,21 @@ static void alc245_fixup_hp_mute_led_coefbit(struct hda_codec *codec,
> snd_hda_gen_add_mute_led_cdev(codec, coef_mute_led_set);
> }
> }
> +static void alc245_fixup_hp_mute_led_v1_coefbit(struct hda_codec *codec,
> + const struct hda_fixup *fix,
> + int action)
Put a blank line before the function.
Could you correct the above and resubmit?
thanks,
Takashi
prev parent reply other threads:[~2025-03-26 7:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 15:05 [PATCH] modified: sound/pci/hda/patch_realtek.c Sharwesh05
2025-03-26 7:26 ` 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=87cye4b6bk.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=sharweshraajan@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 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.