From: Guenter Roeck <linux@roeck-us.net>
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, 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
Subject: Re: [PATCH 5.10 00/11] 5.10.194-rc1 review
Date: Fri, 1 Sep 2023 21:18:28 -0700 [thread overview]
Message-ID: <604baaf6-fd80-4ea5-a52d-27d2f4df50d8@roeck-us.net> (raw)
In-Reply-To: <20230831110830.455765526@linuxfoundation.org>
On Thu, Aug 31, 2023 at 01:09:52PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.194 release.
> There are 11 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 Sat, 02 Sep 2023 11:08:22 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 159 pass: 159 fail: 0
Qemu test results:
total: 487 pass: 487 fail: 0
Tested-by: Guenter Roeck <linux@roeck-us.net>
Guenter
next prev parent reply other threads:[~2023-09-02 4:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 11:09 [PATCH 5.10 00/11] 5.10.194-rc1 review Greg Kroah-Hartman
2023-08-31 11:09 ` [PATCH 5.10 01/11] module: Expose module_init_layout_section() Greg Kroah-Hartman
2023-08-31 11:09 ` [PATCH 5.10 02/11] arm64: module-plts: inline linux/moduleloader.h Greg Kroah-Hartman
2023-08-31 11:09 ` [PATCH 5.10 03/11] arm64: module: Use module_init_layout_section() to spot init sections Greg Kroah-Hartman
2023-08-31 11:09 ` [PATCH 5.10 04/11] ARM: " Greg Kroah-Hartman
2023-08-31 11:09 ` [PATCH 5.10 05/11] mhi: pci_generic: Fix implicit conversion warning Greg Kroah-Hartman
2023-08-31 11:09 ` [PATCH 5.10 06/11] Revert "drm/amdgpu: install stub fence into potential unused fence pointers" Greg Kroah-Hartman
2023-08-31 11:09 ` [PATCH 5.10 07/11] Revert "MIPS: Alchemy: fix dbdma2" Greg Kroah-Hartman
2023-08-31 11:10 ` [PATCH 5.10 08/11] rcu: Prevent expedited GP from enabling tick on offline CPU Greg Kroah-Hartman
2023-08-31 11:10 ` [PATCH 5.10 09/11] rcu-tasks: Fix IPI failure handling in trc_wait_for_one_reader Greg Kroah-Hartman
2023-08-31 11:10 ` [PATCH 5.10 10/11] rcu-tasks: Wait for trc_read_check_handler() IPIs Greg Kroah-Hartman
2023-08-31 11:10 ` [PATCH 5.10 11/11] rcu-tasks: Add trc_inspect_reader() checks for exiting critical section Greg Kroah-Hartman
2023-08-31 20:22 ` [PATCH 5.10 00/11] 5.10.194-rc1 review Florian Fainelli
2023-09-01 9:28 ` Sudip Mukherjee (Codethink)
2023-09-01 11:59 ` Naresh Kamboju
2023-09-01 15:50 ` Shuah Khan
2023-09-01 19:58 ` Jon Hunter
2023-09-02 4:18 ` Guenter Roeck [this message]
2023-09-18 21:33 ` Naresh Kamboju
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=604baaf6-fd80-4ea5-a52d-27d2f4df50d8@roeck-us.net \
--to=linux@roeck-us.net \
--cc=akpm@linux-foundation.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=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;
as well as URLs for NNTP newsgroup(s).