From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.1 000/198] 6.1.132-rc1 review
Date: Tue, 25 Mar 2025 21:05:44 +0100 [thread overview]
Message-ID: <Z+MMmG+f4IGx4e2t@duo.ucw.cz> (raw)
In-Reply-To: <20250325122156.633329074@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1155 bytes --]
Hi!
> This is the start of the stable review cycle for the 6.1.132 release.
> There are 198 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.
Ouch, and we see failure in xfs, too:
In file included from ./include/linux/string.h:5,
3824
from ./include/linux/uuid.h:12,
3825
from ./fs/xfs/xfs_linux.h:10,
3826
from ./fs/xfs/xfs.h:22,
3827
from fs/xfs/libxfs/xfs_alloc.c:6:
3828
fs/xfs/libxfs/xfs_alloc.c: In function '__xfs_free_extent_later':
3829
fs/xfs/libxfs/xfs_alloc.c:2551:51: error: 'mp' undeclared (first use in this function); did you mean 'tp'?
3830
2551 | if (XFS_IS_CORRUPT(mp, !xfs_verify_fsbext(mp, bno, len)))
3831
| ^~
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/9518260339
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2025-03-25 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 12:19 [PATCH 6.1 000/198] 6.1.132-rc1 review Greg Kroah-Hartman
2025-03-25 15:22 ` Naresh Kamboju
2025-03-25 16:07 ` Dragan Simic
2025-03-26 15:31 ` Jon Hunter
2025-03-25 16:52 ` Florian Fainelli
2025-03-25 18:21 ` Miguel Ojeda
2025-03-25 20:02 ` Pavel Machek
2025-03-25 20:05 ` Pavel Machek [this message]
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=Z+MMmG+f4IGx4e2t@duo.ucw.cz \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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=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 \
/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