From: "Luke D. Jones" <luke@ljones.dev>
To: tiwai@suse.com
Cc: perex@perex.cz, sbinding@opensource.cirrus.com,
andy.chi@canonical.com, tcrawford@system76.com,
tangmeng@uniontech.com, p.jungkamp@gmx.net, kasper93@gmail.com,
ruinairas1992@gmail.com, yangyuchi66@gmail.com,
yangyingliang@huawei.com, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, "Luke D. Jones" <luke@ljones.dev>
Subject: [PATCH v2 5/5] Fixes: 31278997add6 (ALSA: hda/realtek - Add headset quirk for Dell DT)
Date: Tue, 4 Jul 2023 16:46:19 +1200 [thread overview]
Message-ID: <20230704044619.19343-6-luke@ljones.dev> (raw)
In-Reply-To: <20230704044619.19343-1-luke@ljones.dev>
Remove an erroneous whitespace.
Signed-off-by: Luke D. Jones <luke@ljones.dev>
---
sound/pci/hda/patch_realtek.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index ba3c113f0be1..1547c40dc7e9 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -5883,7 +5883,7 @@ static void alc_fixup_headset_mode_alc255_no_hp_mic(struct hda_codec *codec,
struct alc_spec *spec = codec->spec;
spec->parse_flags |= HDA_PINCFG_HEADSET_MIC;
alc255_set_default_jack_type(codec);
- }
+ }
else
alc_fixup_headset_mode(codec, fix, action);
}
--
2.41.0
next prev parent reply other threads:[~2023-07-04 4:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 4:46 [PATCH v2 0/5] ALSA: hda/realtek: add extra ROOG laptop quirks Luke D. Jones
2023-07-04 4:46 ` [PATCH v2 1/5] ALSA: hda/realtek: Add quirk for ASUS ROG GX650P Luke D. Jones
2023-07-04 4:46 ` [PATCH v2 2/5] ALSA: hda/realtek: Add quirk for ASUS ROG GA402X Luke D. Jones
2023-07-04 4:46 ` [PATCH v2 3/5] ALSA: hda/realtek: Amend G634 quirk to enable rear speakers Luke D. Jones
2023-07-04 4:46 ` [PATCH v2 4/5] ALSA: hda/realtek: Add quirk for ASUS ROG G614Jx Luke D. Jones
2023-07-04 4:46 ` Luke D. Jones [this message]
2023-07-04 6:44 ` [PATCH v2 0/5] ALSA: hda/realtek: add extra ROOG laptop quirks Takashi Iwai
2023-07-04 23:18 ` Luke Jones
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=20230704044619.19343-6-luke@ljones.dev \
--to=luke@ljones.dev \
--cc=alsa-devel@alsa-project.org \
--cc=andy.chi@canonical.com \
--cc=kasper93@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=p.jungkamp@gmx.net \
--cc=perex@perex.cz \
--cc=ruinairas1992@gmail.com \
--cc=sbinding@opensource.cirrus.com \
--cc=tangmeng@uniontech.com \
--cc=tcrawford@system76.com \
--cc=tiwai@suse.com \
--cc=yangyingliang@huawei.com \
--cc=yangyuchi66@gmail.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.