From: Miguel Ojeda <ojeda@kernel.org>
To: gregkh@linuxfoundation.org
Cc: akpm@linux-foundation.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/127] 6.1.45-rc1 review
Date: Thu, 10 Aug 2023 23:17:37 +0200 [thread overview]
Message-ID: <20230810211737.8646-1-ojeda@kernel.org> (raw)
In-Reply-To: <20230809103636.615294317@linuxfoundation.org>
On Wed, Aug 09, 2023 at 12:39:47PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.45 release.
> There are 127 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.
For Rust, build tested and booted to see the trivial Rust sample
output in the kernel log:
Tested-by: Miguel Ojeda <ojeda@kernel.org> # Rust
Cheers,
Miguel
next prev parent reply other threads:[~2023-08-10 21:18 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 10:39 [PATCH 6.1 000/127] 6.1.45-rc1 review Greg Kroah-Hartman
2023-08-09 13:42 ` Joel Fernandes
2023-08-09 17:08 ` SeongJae Park
2023-08-09 21:38 ` Florian Fainelli
2023-08-10 3:54 ` Bagas Sanjaya
2023-08-10 5:12 ` Takeshi Ogasawara
2023-08-10 7:06 ` Ron Economos
2023-08-10 10:15 ` Guenter Roeck
2023-08-11 10:06 ` Greg Kroah-Hartman
2023-08-10 10:28 ` Conor Dooley
2023-08-10 16:14 ` Guenter Roeck
2023-08-11 10:07 ` Greg Kroah-Hartman
2023-08-11 10:26 ` Guenter Roeck
2023-08-10 21:17 ` Miguel Ojeda [this message]
2023-08-11 3:22 ` Naresh Kamboju
2023-08-11 3:36 ` Nathan Chancellor
2023-08-11 3:41 ` Guenter Roeck
2023-08-11 4:13 ` Nathan Chancellor
2023-08-13 11:02 ` Borislav Petkov
2023-08-14 16:52 ` Nathan Chancellor
2023-08-14 11:17 ` Thierry Reding
2023-08-14 12:58 ` Conor Dooley
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=20230810211737.8646-1-ojeda@kernel.org \
--to=ojeda@kernel.org \
--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=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