linux-kernel - RE: [PATCH AUTOSEL 5.14 058/252] spi: imx: fix ERR009165

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] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 10 Sep 2021 03:30:27 +0000
From:   Robin Gong <yibin.gong@....com>
To:     Fabio Estevam <festevam@...il.com>,
        Lucas Stach <l.stach@...gutronix.de>
CC:     Sasha Levin <sashal@...nel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>, Mark Brown <broonie@...nel.org>,
        Shawn Guo <shawnguo@...nel.org>,
        linux-spi <linux-spi@...r.kernel.org>,
        "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH AUTOSEL 5.14 058/252] spi: imx: fix ERR009165

> Hi Lucas,
> 
> On Thu, Sep 9, 2021 at 1:43 PM Lucas Stach <l.stach@...gutronix.de> wrote:
> >
> > Hi Sasha,
> >
> > Am Donnerstag, dem 09.09.2021 um 07:37 -0400 schrieb Sasha Levin:
> > > From: Robin Gong <yibin.gong@....com>
> > >
> > > [ Upstream commit 980f884866eed4dda2a18de888c5a67dde67d640 ]
> > >
> > > Change to XCH  mode even in dma mode, please refer to the below
> > > errata:
> > > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fww
> > >
> w.nxp.com%2Fdocs%2Fen%2Ferrata%2FIMX6DQCE.pdf&amp;data=04%7C01
> %7Cyib
> > >
> in.gong%40nxp.com%7C39f3117d59434df46fc108d973b1bb3e%7C686ea1d3
> bc2b4
> > >
> c6fa92cd99c5c301635%7C0%7C1%7C637668029454898655%7CUnknown%7
> CTWFpbGZ
> > >
> sb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn
> 0
> > > %3D%7C1000&amp;sdata=NxCByvu4qCGniWnXccSxLNy9ilvQhFpid7O9Ag
> 1HloI%3D&
> > > amp;reserved=0
> > >
> >
> > This patch is part of a quite extensive series touching multiple
> > drivers and devicetree descriptions and will do more harm than good if
> > backported without the rest of the series. The options here are:
> > a) backport the entire series (this will most likely not match the
> > stable criteria)
> > b) drop the patch from the stable queue
> 
> Yes, I agree. I prefer going with option b).
Agree, vote for option b.