From: "Theodore Ts'o" <tytso@mit.edu>
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, hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.12 000/156] 6.12.9-rc1 review
Date: Tue, 7 Jan 2025 10:47:25 -0500 [thread overview]
Message-ID: <20250107154725.GA1419052@mit.edu> (raw)
In-Reply-To: <20250106151141.738050441@linuxfoundation.org>
On Mon, Jan 06, 2025 at 04:14:46PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.12.9 release.
> There are 156 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.
No problems noted for ext4 with 6.12.9-rc1. I don't speak officially
for xfs, but I didn't notice any new problems there either.
Cheers,
- Ted
next prev parent reply other threads:[~2025-01-07 15:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 15:14 [PATCH 6.12 000/156] 6.12.9-rc1 review Greg Kroah-Hartman
2025-01-06 16:41 ` Ronald Warsow
2025-01-06 18:24 ` Pavel Machek
2025-01-06 20:26 ` Florian Fainelli
2025-01-06 23:18 ` Shuah Khan
2025-01-07 23:14 ` Shuah Khan
2025-01-06 23:31 ` Justin Forbes
2025-01-07 1:08 ` SeongJae Park
2025-01-07 1:39 ` Peter Schneider
2025-01-07 6:56 ` Ron Economos
2025-01-07 8:33 ` Naresh Kamboju
2025-01-07 9:36 ` Luna Jernberg
2025-01-07 10:29 ` Christian Heusel
2025-01-07 11:36 ` Takeshi Ogasawara
2025-01-07 12:44 ` Jon Hunter
2025-01-07 15:12 ` Mark Brown
2025-01-07 15:47 ` Theodore Ts'o [this message]
2025-01-07 16:56 ` Harshit Mogalapalli
2025-01-07 21:24 ` [PATCH 6.12] " Hardik Garg
2025-01-08 12:41 ` [PATCH 6.12 000/156] " Muhammad Usama Anjum
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=20250107154725.GA1419052@mit.edu \
--to=tytso@mit.edu \
--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=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