From: Christoph Biedl <linux-kernel.bfrz@manchmal.in-ulm.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,
pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org
Subject: Re: [PATCH 6.10 000/375] 6.10.10-rc1 review
Date: Tue, 10 Sep 2024 21:50:22 +0200 [thread overview]
Message-ID: <1725997627@msgid.manchmal.in-ulm.de> (raw)
In-Reply-To: <20240910092622.245959861@linuxfoundation.org>
Greg Kroah-Hartman wrote...
> This is the start of the stable review cycle for the 6.10.10 release.
> There are 375 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.
Can confirm again this ends the issues on parisc, thanks to:
> Helge Deller <deller@gmx.de>
> parisc: Delay write-protection until mark_rodata_ro() call
Kind regards,
Christoph (who would like to do more -rc testing, but the time ...)
next prev parent reply other threads:[~2024-09-10 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 9:26 [PATCH 6.10 000/375] 6.10.10-rc1 review Greg Kroah-Hartman
2024-09-10 9:30 ` [PATCH 6.10 213/375] wifi: rtw88: usb: schedule rx work after everything is set up Greg Kroah-Hartman
2024-09-10 19:50 ` Christoph Biedl [this message]
2024-09-10 20:52 ` [PATCH 6.10 000/375] 6.10.10-rc1 review Florian Fainelli
2024-09-10 22:02 ` Mark Brown
2024-09-10 23:13 ` Shuah Khan
2024-09-11 9:46 ` Naresh Kamboju
2024-09-11 12:22 ` Christian Heusel
2024-09-11 19:31 ` Justin Forbes
2024-09-11 20:21 ` Pavel Machek
2024-09-12 0:12 ` Ron Economos
2024-09-12 7:18 ` Kexy Biscuit
2024-09-12 7:19 ` Jon Hunter
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=1725997627@msgid.manchmal.in-ulm.de \
--to=linux-kernel.bfrz@manchmal.in-ulm.de \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--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=pavel@denx.de \
--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