[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-id: <288a2a10-137d-49b5-8d44-feb18f5696d2@augustwikerfors.se>
Date: Wed, 27 Sep 2023 21:07:49 +0200
From: August Wikerfors <git@...ustwikerfors.se>
To: Sven Frotscher <sven.frotscher@...il.com>
Cc: broonie@...nel.org, alsa-devel@...a-project.org,
lgirdwood@...il.com, linux-kernel@...r.kernel.org,
mario.limonciello@....com, regressions@...ts.linux.dev
Subject: Re: [PATCH] ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM
On 2023-09-27 20:49, Sven Frotscher wrote:
> Hello,
>
> > > Signed-off-by: Sven Frotscher <sven.frotscher@...il.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@...r.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?
AFAIK either way is fine, separate thread seems more common though.
Powered by blists - more mailing lists