Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.34 as permitted sender) client-ip=23.128.96.34;
Message-id: <288a2a10-137d-49b5-8d44-feb18f5696d2@augustwikerfors.se>
Date:   Wed, 27 Sep 2023 21:07:49 +0200
MIME-version: 1.0
Subject: Re: [PATCH] ASoC: amd: yc: Fix non-functional mic on Lenovo 82YM
Content-language: en-US
To:     Sven Frotscher <sven.frotscher@gmail.com>
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
References: <R5KN1S.18M6QDS4T9PY1@gmail.com>
 <e8479eff-a5cb-41b0-8bf6-bcc20ccbecfb@augustwikerfors.se>
 <2ZQN1S.P7M0RX306S1D3@gmail.com>
From:   August Wikerfors <git@augustwikerfors.se>
In-reply-to: <2ZQN1S.P7M0RX306S1D3@gmail.com>
Content-type: text/plain; charset=UTF-8; format=flowed
Content-transfer-encoding: 7bit
Reporting-Meta: AAEINYZ3dhLONaY9tyI3lZesZ89O1+5jgsVyp4dMSkyYuppG/dP70jN8lViyntJq
 I5DRJNIssIA14bGdujZ1eWSb5GPSDteTcc0OYm2P/vPIEC9ARA2gsO65cnzcFPg8
 XoaZOQlsMmAzTLz1oOLdPQpP/ITKpRaE1JUW9YqSSFws8mXptE9sAaM9MCSb5maS
 ok6cfXc33mDZX27kNFAewOfcRHIsKX/0QRPI7CGgev/nC3WFMBMHAxkigTiI6fI1
 f4LLRvaryePOq5y5bsQHjg9qf2ldQboX9Gmorg79URbdtOLQy0o4YcJKWHOwfr2b
 Y9b7muMt5sY1z3mUYueqh0z5+NvtqSmGO3TKlcLd2fbo+hWXxxyp1kyFPknb+MX9
 gzc3YD56+s5qj0nG4jlmEu36kUfc0tkm/q6iz/+WQbt0sBqv+Wn8J/nz1EUrdygh JVcZcw==
Precedence: bulk

On 2023-09-27 20:49, Sven Frotscher wrote:
> 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?
AFAIK either way is fine, separate thread seems more common though.