linux-kernel - Re: [PATCH v2 1/1] spi-mxs: Fix chipselect glitch

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <5ab9b62a-6577-4a3f-9dfe-c7362bf725db@gmx.net>
Date: Wed, 4 Dec 2024 14:27:24 +0100
From: Stefan Wahren <wahrenst@....net>
To: Fabio Estevam <festevam@...il.com>, Ralf Schlatterbeck <rsc@...tux.com>
Cc: Mark Brown <broonie@...nel.org>, Shawn Guo <shawnguo@...nel.org>,
 Sascha Hauer <s.hauer@...gutronix.de>,
 Pengutronix Kernel Team <kernel@...gutronix.de>,
 NXP Linux Team <linux-imx@....com>, linux-spi@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
 Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH v2 1/1] spi-mxs: Fix chipselect glitch

Hi,

Am 13.02.24 um 18:22 schrieb Fabio Estevam:
> Hi Ralf,
>
> On Tue, Feb 13, 2024 at 2:07 PM Ralf Schlatterbeck <rsc@...tux.com> wrote:
>> On Fri, Feb 02, 2024 at 12:53:30PM +0100, Ralf Schlatterbeck wrote:
>>> There was a change in the mxs-dma engine that uses a new custom flag.
>>> The change was not applied to the mxs spi driver.
>>> This results in chipselect being deasserted too early.
>>> This fixes the chipselect problem by using the new flag in the mxs-spi
>>> driver.
>>>
>>> Fixes: ceeeb99cd821 ("dmaengine: mxs: rename custom flag")
>>> Signed-off-by: Ralf Schlatterbeck <rsc@...tux.com>
>>> ---
>>> For oscilloscope screenshots and a verbose explanation see my blog post
>>> at https://blog.runtux.com/posts/2024/02/01/
> I suggest putting the link to your detailed explanation into the
> commit log as this is useful information.
>
> Reviewed-by: Fabio Estevam <festevam@...il.com>
I noticed that this patch hasn't applied to stable yet.

Are there reason for not doing this or is it just because the patch
missed the Cc: stable@...r.kernel.org ?