From: Pavel Machek <pavel@nabladev.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: gregkh@linuxfoundation.org, achill@achill.org,
akpm@linux-foundation.org, broonie@kernel.org, conor@kernel.org,
f.fainelli@gmail.com, hargar@microsoft.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux@roeck-us.net,
lkft-triage@lists.linaro.org, patches@kernelci.org,
patches@lists.linux.dev, pavel@nabladev.com, rwarsow@gmx.de,
shuah@kernel.org, sr@sladewatkins.com, stable@vger.kernel.org,
sudipm.mukherjee@gmail.com, torvalds@linux-foundation.org,
Anuj Gupta <anuj20.g@samsung.com>,
Kanchan Joshi <joshi.k@samsung.com>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [PATCH 6.12 000/272] 6.12.92-rc1 review
Date: Fri, 29 May 2026 10:27:21 +0200 [thread overview]
Message-ID: <ahlN6TPTgMwBT9_d@duo.ucw.cz> (raw)
In-Reply-To: <20260529060918.123155-1-ojeda@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
Hi!
> > This is the start of the stable review cycle for the 6.12.92 release.
> > There are 272 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 Sat, 30 May 2026 19:45:52 +0000.
> > Anything received after that time might be too late.
>
> Boot-tested under QEMU for Rust x86_64, arm64 and riscv64; built-tested
> for loongarch64:
>
> Tested-by: Miguel Ojeda <ojeda@kernel.org>
>
> I am seeing:
>
> In file included from kernel/trace/blktrace.c:23:
> In file included from kernel/trace/../../block/blk.h:5:
> ./include/linux/bio-integrity.h:101:12: error: unused function 'bio_integrity_map_user' [-Werror,-Wunused-function]
> 101 | static int bio_integrity_map_user(struct bio *bio, struct iov_iter *iter)
> | ^~~~~~~~~~~~~~~~~~~~~~
>
We see that, too:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/14592368004
We don't see the problem on 6.6, 6.18 or 7.0-stable.
Best regards,
Pavel
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2026-05-29 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 19:46 Greg Kroah-Hartman
2026-05-29 3:23 ` Dominique Martinet
2026-05-29 5:39 ` Ron Economos
2026-05-29 6:09 ` Miguel Ojeda
2026-05-29 8:27 ` Pavel Machek [this message]
2026-05-29 12:44 ` Sasha Levin
2026-05-29 19:33 ` Florian Fainelli
2026-05-29 10:59 ` Peter Schneider
2026-05-29 6:23 ` Francesco Dolcini
2026-05-29 6:33 ` Brett A C Sheffield
2026-05-29 19:19 ` Florian Fainelli
2026-05-29 21:50 ` Mark Brown
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=ahlN6TPTgMwBT9_d@duo.ucw.cz \
--to=pavel@nabladev.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=anuj20.g@samsung.com \
--cc=axboe@kernel.dk \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=hch@lst.de \
--cc=jonathanh@nvidia.com \
--cc=joshi.k@samsung.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=ojeda@kernel.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
Powered by JetHome