From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Manuel Lauss <manuel.lauss@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
stable <stable@vger.kernel.org>,
patches@lists.linux.dev, LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
shuah@kernel.org, patches@kernelci.org,
lkft-triage@lists.linaro.org, Pavel Machek <pavel@denx.de>,
jonathanh@nvidia.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Subject: Re: [PATCH 5.10 00/84] 5.10.193-rc1 review
Date: Thu, 31 Aug 2023 17:13:31 +0200 [thread overview]
Message-ID: <2023083107-calcium-slab-89a5@gregkh> (raw)
In-Reply-To: <4a69c0c0-5e8a-9a3a-6527-3eb7e51a955e@gmail.com>
On Thu, Aug 31, 2023 at 07:54:06AM -0700, Florian Fainelli wrote:
>
>
> On 8/31/2023 3:31 AM, Greg Kroah-Hartman wrote:
> > On Wed, Aug 30, 2023 at 07:38:09PM +0200, Manuel Lauss wrote:
> > > Hello all,
> > >
> > > Florian Fainelli <f.fainelli@gmail.com> schrieb am Mi., 30. Aug. 2023, 19:07:
> > > >
> > > > + Manuel,
> > > >
> > > > On 8/30/23 09:01, Guenter Roeck wrote:
> > > > > On 8/30/23 03:52, Greg Kroah-Hartman wrote:
> > > > > > 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?
> > > > > >
> > > > >
> > > > > Nothing. I started to build this configuration and tracked down the
> > > > > problem after the build failure was reported by others. Sorry, I didn't
> > > > > initially realize that this is an old problem.
> > > >
> > > > We could back port 6d4e9a8efe3d59f31367d79e970c2f328da139a4 ("driver
> > > > core: lift dma_default_coherent into common code") but that won't work
> > > > too well on 4.14 or 4.19. I believe it would be simpler to adjust the
> > > > branches with this patch, Manuel does that work?
> > >
> > > Please drop this patch from all stable releases. I didn't CC stable
> > > when I submitted it,
> > > and have no idea why it ended up there anyway.
> > > It was intended to fix a problem initially found in 5.18 (I think).
> >
> > I'm going to revert it now, thanks!
>
> I prepared reverts yesterday that I can send out if you want?
I think this is all taken care of in the latest -rc releases, right? If
I missed anything, then yes, reverts would be great to have.
thanks,
greg k-h
next prev parent reply other threads:[~2023-08-31 15:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 10:13 Greg Kroah-Hartman
2023-08-28 16:42 ` Guenter Roeck
2023-08-30 10:52 ` Greg Kroah-Hartman
2023-08-30 16:01 ` Guenter Roeck
2023-08-30 17:07 ` Florian Fainelli
2023-08-30 17:38 ` Manuel Lauss
2023-08-31 10:31 ` Greg Kroah-Hartman
2023-08-31 14:54 ` Florian Fainelli
2023-08-31 15:13 ` Greg Kroah-Hartman [this message]
2023-08-28 17:24 ` Guenter Roeck
2023-08-30 10:53 ` Greg Kroah-Hartman
2023-08-29 9:06 ` luomeng
2023-08-29 9:15 ` Naresh Kamboju
2023-08-29 11:42 ` Sudip Mukherjee (Codethink)
2023-08-29 14:22 ` Shuah Khan
2023-08-29 18:07 ` Florian Fainelli
2023-08-30 2:02 ` Guenter Roeck
2023-08-30 10:24 ` Jon Hunter
2023-08-30 11:29 ` Pavel Machek
2023-08-30 13:16 ` Joel Fernandes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2023083107-calcium-slab-89a5@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=manuel.lauss@gmail.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=tsbogend@alpha.franken.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome