From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.org, allen.lkml@gmail.com,
broonie@kernel.org, conor@kernel.org, f.fainelli@gmail.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@denx.de,
rwarsow@gmx.de, shuah@kernel.org, srw@sladewatkins.net,
stable@vger.kernel.org, sudipm.mukherjee@gmail.com,
torvalds@linux-foundation.org, Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH 6.1 000/791] 6.1.113-rc2 review
Date: Wed, 16 Oct 2024 14:51:44 +0200 [thread overview]
Message-ID: <20241016125144.139393-1-ojeda@kernel.org> (raw)
In-Reply-To: <20241015112501.498328041@linuxfoundation.org>
On Tue, 15 Oct 2024 13:26:04 +0200 Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> This is the start of the stable review cycle for the 6.1.113 release.
> There are 791 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 Thu, 17 Oct 2024 11:22:41 +0000.
> Anything received after that time might be too late.
Boot-tested under QEMU for Rust x86_64:
Tested-by: Miguel Ojeda <ojeda@kernel.org>
Thanks!
Cheers,
Miguel
next prev parent reply other threads:[~2024-10-16 12:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-15 11:26 [PATCH 6.1 000/791] 6.1.113-rc2 review Greg Kroah-Hartman
2024-10-15 15:34 ` Ron Economos
2024-10-15 17:33 ` Florian Fainelli
2024-10-16 8:15 ` Naresh Kamboju
2024-10-16 8:50 ` Naresh Kamboju
2024-10-16 9:21 ` Pavel Machek
2024-10-16 10:01 ` Jon Hunter
2024-10-16 12:51 ` Miguel Ojeda [this message]
2024-10-17 12:30 ` Muhammad Usama Anjum
2024-10-19 15:17 ` Guenter Roeck
2024-10-21 9:45 ` Greg Kroah-Hartman
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=20241016125144.139393-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.