From: Pavel Machek <pavel@nabladev.com>
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,
pavel@nabladev.com, 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 6.1 0000/1887] 6.1.191-rc1 review
Date: Wed, 28 Oct 2026 23:16:47 +0100 [thread overview]
Message-ID: <auJ0T2vTCe4Jhomj@duo.ucw.cz> (raw)
In-Reply-To: <20261028170459.200466217@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
Hi!
> This is the start of the stable review cycle for the 6.1.191 release.
> There are 1887 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.
We get build failure in Bluetooth (we probably see the other reported
bugs, too, I did not check):
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/17550762421
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/3000620758
Best regards,
Pavel
net/bluetooth/mgmt.c: In function 'set_mesh_sync':
3514
18:36:58
net/bluetooth/mgmt.c:2188:36: error: implicit declaration of function '__struct_size'; did you mean 'struct_size'? [-Werror=implicit-function-declaration]
3515
18:36:58
2188 | memcpy(cp, cmd->param, min(__struct_size(cp), len));
3516
18:36:58
| ^~~~~~~~~~~~~
3517
18:36:58
./include/linux/minmax.h:92:27: note: in definition of macro '__careful_cmp_once'
3518
18:36:58
92 | __auto_type ux = (x); __auto_type uy = (y); \
3519
18:36:58
| ^
3520
18:36:58
./include/linux/minmax.h:105:25: note: in expansion of macro '__careful_cmp'
3521
18:36:58
105 | #define min(x, y) __careful_cmp(min, x, y)
3522
18:36:58
| ^~~~~~~~~~~~~
3523
18:36:58
net/bluetooth/mgmt.c:2188:32: note: in expansion of macro 'min'
3524
18:36:58
2188 | memcpy(cp, cmd->param, min(__struct_size(cp), len));
3525
18:36:58
| ^~~
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-10-28 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 16:34 Greg Kroah-Hartman
2026-10-28 17:04 ` [PATCH 6.1 1779/1887] hwmon: (drivetemp) Fix driver producing garbage data when SCSI errors occur Greg Kroah-Hartman
2026-10-28 19:54 ` [PATCH 6.1 0000/1887] 6.1.191-rc1 review Brett A C Sheffield
2026-10-28 20:44 ` Brett A C Sheffield
2026-10-29 0:25 ` Peter Schneider
2026-10-28 21:12 ` Florian Fainelli
2026-10-28 21:26 ` Florian Fainelli
2026-10-29 2:53 ` Sasha Levin
2026-10-28 22:16 ` Pavel Machek [this message]
2026-10-29 0:19 ` Peter Schneider
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=auJ0T2vTCe4Jhomj@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=achill@achill.org \
--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=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
all inboxes | Powered by JetHome®