From: Woody Suwalski <terraluna977@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: 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@nabladev.com,
jonathanh@nvidia.com, 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 5.10 000/160] 5.10.249-rc2 review
Date: Thu, 5 Feb 2026 22:28:30 -0500 [thread overview]
Message-ID: <245e7367-8ef2-daa0-b856-540870e75254@gmail.com> (raw)
In-Reply-To: <20260205143430.733102763@linuxfoundation.org>
Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.249 release.
> There are 160 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.
>
>
Tested a 32-bit build on an i386 computer. No problems noticed.
Tested-by: Woody Suwalski <terraluna977@gmail.com>
next prev parent reply other threads:[~2026-02-06 3:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 14:44 [PATCH 5.10 000/160] 5.10.249-rc2 review Greg Kroah-Hartman
2026-02-05 17:21 ` Brett A C Sheffield
2026-02-05 19:58 ` Florian Fainelli
2026-02-05 21:11 ` Mark Brown
2026-02-06 3:28 ` Woody Suwalski [this message]
2026-02-06 4:24 ` Barry K. Nathan
2026-02-06 10:59 ` Jon Hunter
2026-02-06 12:19 ` Jeffrin Thalakkottoor
2026-02-06 12:30 ` Greg Kroah-Hartman
2026-02-06 12:59 ` Jeffrin Thalakkottoor
2026-02-06 13:18 ` Greg Kroah-Hartman
2026-02-06 16:52 ` Jeffrin Thalakkottoor
2026-02-06 22:28 ` Pavel Machek
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=245e7367-8ef2-daa0-b856-540870e75254@gmail.com \
--to=terraluna977@gmail.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=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@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