mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sven Frotscher <sven.frotscher@gmail.com>
To: August Wikerfors <git@augustwikerfors.se>
Cc: broonie@kernel.org, alsa-devel@alsa-project.org,
	lgirdwood@gmail.com, linux-kernel@vger.kernel.org,
	mario.limonciello@amd.com, regressions@lists.linux.dev
Subject: Re: [PATCH] ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM
Date: Wed, 27 Sep 2023 20:49:50 +0200	[thread overview]
Message-ID: <2ZQN1S.P7M0RX306S1D3@gmail.com> (raw)
In-Reply-To: <e8479eff-a5cb-41b0-8bf6-bcc20ccbecfb@augustwikerfors.se>

Hello,

 > > Signed-off-by: Sven Frotscher <sven.frotscher@gmail.com>
 > Since this fixes a regression caused by commit c008323fe361 which has
 > been backported to stable, please add "Fixes:" and "Cc:" tags above 
the
 > "Signed-off-by:" tag to ensure the fix also gets backported in a 
timely
 > manner [1]:
 >
 > Fixes: c008323fe361 ("ASoC: amd: yc: Fix a non-functional mic on 
Lenovo 82SJ")
 > Cc: stable@vger.kernel.org
I will.

 > > +>..>...>...DMI_MATCH(DMI_BOARD_VENDOR, "LENOVO"),
 > > +>..>...>...DMI_MATCH(DMI_PRODUCT_NAME, "82YM"),
 > Your e-mail client seems to have mangled the leading whitespace here,
 > which will prevent the patch from applying cleanly.
My e-mail client isn't the problem here, but my Vim syntax highlighting
for tabs... I should've noticed that when copy-pasting from test e-mail
to patch e-mail via Vim.

Should I reply to this thread with a [PATCH v2] message or create a new
thread?
Anyway, thank you for pointing out these issues.

Regards,
Sven



  reply	other threads:[~2023-09-27 18:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-27 16:22 Sven Frotscher
2023-09-27 17:41 ` August Wikerfors
2023-09-27 18:49   ` Sven Frotscher [this message]
2023-09-27 19:07     ` August Wikerfors

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=2ZQN1S.P7M0RX306S1D3@gmail.com \
    --to=sven.frotscher@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=git@augustwikerfors.se \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=regressions@lists.linux.dev \
    /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®