From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Ron Economos <re@w6rz.net>
Cc: stable@vger.kernel.org, patches@lists.linux.dev,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
patches@kernelci.org, lkft-triage@lists.linaro.org,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
sr@sladewatkins.com
Subject: Re: [PATCH 5.15 000/551] 5.15.198-rc2 review
Date: Sat, 17 Jan 2026 16:00:25 +0100 [thread overview]
Message-ID: <2026011710-grinch-busboy-dda1@gregkh> (raw)
In-Reply-To: <2aaa124e-4322-43cc-b155-2011b94b449c@w6rz.net>
On Fri, Jan 16, 2026 at 10:36:37PM -0800, Ron Economos wrote:
> On 1/16/26 03:13, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.198 release.
> > There are 551 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 Sun, 18 Jan 2026 11:09:20 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.15.198-rc2.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.15.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> My HiFive Unmatched target (which has a Cadence Ethernet controller) fails to start the network interface with the following messages:
>
> [ 121.778662] macb 10090000.ethernet end0: inconsistent Rx descriptor chain
> [ 122.373760] macb 10090000.ethernet end0: inconsistent Rx descriptor chain
> [ 122.383421] macb 10090000.ethernet end0: inconsistent Rx descriptor chain
> [ 122.389481] macb 10090000.ethernet end0: inconsistent Rx descriptor chain
> [ 122.610641] macb 10090000.ethernet end0: inconsistent Rx descriptor chain
>
> Reverting commit "net: macb: Relocate mog_init_rings() callback from
> macb_mac_link_up() to macb_open()" f934e5d7caad6ae0a081352e91cbd7f0284ad9b3
> solves the issue.
Thanks for the info, I'll go drop this from 5.15.y and 5.10.y as well.
greg k-h
next prev parent reply other threads:[~2026-01-17 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 11:13 [PATCH 5.15 000/551] 5.15.198-rc2 review Greg Kroah-Hartman
2026-01-16 11:49 ` Brett A C Sheffield
2026-01-16 12:25 ` Jon Hunter
2026-01-16 19:21 ` Florian Fainelli
2026-01-16 19:21 ` Mark Brown
2026-01-16 19:25 ` Hardik Garg
2026-01-17 6:36 ` Ron Economos
2026-01-17 15:00 ` Greg Kroah-Hartman [this message]
2026-01-19 10:26 ` Jeffrin Thalakkottoor
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=2026011710-grinch-busboy-dda1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=re@w6rz.net \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=sr@sladewatkins.com \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
/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