[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2023083014-barley-upscale-518e@gregkh>
Date: Wed, 30 Aug 2023 12:52:19 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Guenter Roeck <linux@...ck-us.net>
Cc: stable@...r.kernel.org, patches@...ts.linux.dev,
linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
akpm@...ux-foundation.org, shuah@...nel.org, patches@...nelci.org,
lkft-triage@...ts.linaro.org, pavel@...x.de, jonathanh@...dia.com,
f.fainelli@...il.com, sudipm.mukherjee@...il.com,
srw@...dewatkins.net, rwarsow@....de, conor@...nel.org,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Subject: Re: [PATCH 5.10 00/84] 5.10.193-rc1 review
On Mon, Aug 28, 2023 at 09:42:11AM -0700, Guenter Roeck wrote:
> On 8/28/23 03:13, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.10.193 release.
> > There are 84 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Wed, 30 Aug 2023 10:11:30 +0000.
> > Anything received after that time might be too late.
> >
>
> FWIW, commit 619672bf2d04 ("MIPS: Alchemy: fix dbdma2") should be reverted
> v5.10.y since it doesn't fix anything but breaks the build for affected boards
> completely.
>
> arch/mips/alchemy/common/dbdma.c: In function 'au1xxx_dbdma_put_source':
> arch/mips/alchemy/common/dbdma.c:632:14: error: 'dma_default_coherent' undeclared
>
> There is no 'dma_default_coherent' in v5.10.y.
But that was added in 5.10.185, from back in June. What changed to
suddenly cause this to fail now?
As this isn't a new regression, I'll hold off on fixing this here and
just do so in a future release.
thanks,
greg k-h
Powered by blists - more mailing lists