From: Jon Hunter <jonathanh@nvidia.com>
To: Pavel Machek <pavel@nabladev.com>,
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,
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.12 0000/1376] 6.12.110-rc1 review
Date: Sun, 13 Sep 2026 12:59:10 +0100 [thread overview]
Message-ID: <f8e1fe51-03f1-4158-80cd-2b462624da3a@nvidia.com> (raw)
In-Reply-To: <aqWnzsSIMkyM46NV@duo.ucw.cz>
On 12/09/2026 20:28, Pavel Machek wrote:
> Hi!
>
>> This is the start of the stable review cycle for the 6.12.110 release.
>> There are 1376 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 errors in -cip testing:
>
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/2842911949
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/jobs/16461797877
>
> drivers/soc/ti/knav_qmss_queue.c: In function 'knav_queue_probe':
> drivers/soc/ti/knav_qmss_queue.c:1874:9: error: 'knav_qdev' undeclared (first use in this function); did you mean 'knav_queue'?
I am seeing the same for 6.12 and 6.18. Appears to be this commit ...
# first bad commit: [4e91398b6ae1dde1824bcf3d19b4237773f31e68] soc: ti: knav_qmss: Remove debugfs file on teardown
Jon
--
nvpublic
next prev parent reply other threads:[~2026-09-13 11:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-12 6:40 Greg Kroah-Hartman
2026-09-12 11:51 ` Brett A C Sheffield
2026-09-12 16:27 ` Peter Schneider
2026-09-12 19:28 ` Pavel Machek
2026-09-13 11:59 ` Jon Hunter [this message]
2026-09-14 9:47 ` Greg Kroah-Hartman
2026-09-12 21:11 ` Dominique Martinet
2026-09-13 13:00 ` Barry K. Nathan
2026-09-13 23:00 ` Ron Economos
2026-09-14 5:06 ` Miguel Ojeda
2026-09-14 5:09 ` Francesco Dolcini
2026-09-14 18:01 ` Florian Fainelli
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=f8e1fe51-03f1-4158-80cd-2b462624da3a@nvidia.com \
--to=jonathanh@nvidia.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=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@nabladev.com \
--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®