From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: 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,
Miguel Ojeda <ojeda@kernel.org>, Gary Guo <gary@garyguo.net>,
Tim Kovalenko <tim.kovalenko@proton.me>,
Danilo Krummrich <dakr@kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
nouveau@lists.freedesktop.org,
Huacai Chen <chenhuacai@kernel.org>,
WANG Xuerui <kernel@xen0n.name>,
loongarch@lists.linux.dev
Subject: Re: [PATCH 6.19 000/220] 6.19.10-rc1 review
Date: Wed, 25 Mar 2026 02:34:47 +0100 [thread overview]
Message-ID: <20260325013447.66771-1-ojeda@kernel.org> (raw)
In-Reply-To: <20260323134504.575022936@linuxfoundation.org>
On Mon, 23 Mar 2026 14:42:57 +0100 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.19.10 release.
> There are 220 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 Wed, 25 Mar 2026 13:44:33 +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>
For loongarch64, I am seeing:
drivers/gpu/nova-core/nova_core.o: warning: objtool: _RNvMs1_NtNtCskfHXyXj90Gn_9nova_core3gsp4cmdqNtB5_4Cmdq3new+0x2c8: return with modified stack frame
Which got fixed in mainline by:
c7940c8bf215 ("gpu: nova-core: fix stack overflow in GSP memory allocation")
But 1) this is just for loongarch64, 2) Nova is still being developed
and 3) it is just for 6.19.y, so that is probably there was no Cc:
stable@. Anyway, Cc'ing here.
Cc: Gary Guo <gary@garyguo.net>
Cc: Tim Kovalenko <tim.kovalenko@proton.me>
Cc: Danilo Krummrich <dakr@kernel.org>
Cc: Alexandre Courbot <acourbot@nvidia.com>
Cc: nouveau@lists.freedesktop.org
Cc: Huacai Chen <chenhuacai@kernel.org>
Cc: WANG Xuerui <kernel@xen0n.name>
Cc: loongarch@lists.linux.dev
Thanks!
Cheers,
Miguel
next parent reply other threads:[~2026-03-25 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260323134504.575022936@linuxfoundation.org>
2026-03-25 1:34 ` Miguel Ojeda [this message]
2026-03-25 1:36 ` [PATCH 6.19 000/220] 6.19.10-rc1 review Miguel Ojeda
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=20260325013447.66771-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--cc=achill@achill.org \
--cc=acourbot@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=conor@kernel.org \
--cc=dakr@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gary@garyguo.net \
--cc=gregkh@linuxfoundation.org \
--cc=hargar@microsoft.com \
--cc=jonathanh@nvidia.com \
--cc=kernel@xen0n.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=loongarch@lists.linux.dev \
--cc=nouveau@lists.freedesktop.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=tim.kovalenko@proton.me \
--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