From: Conor Dooley <conor.dooley@microchip.com>
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>
Subject: Re: [PATCH 6.1 000/132] 6.1.34-rc1 review
Date: Tue, 13 Jun 2023 09:47:35 +0100 [thread overview]
Message-ID: <20230613-curdle-varied-0e920e75d1d9@wendy> (raw)
In-Reply-To: <20230612101710.279705932@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
On Mon, Jun 12, 2023 at 12:25:34PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.34 release.
> There are 132 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-by: Conor Dooley <conor.dooley@microchip.com>
Thanks,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-06-13 8:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 10:25 Greg Kroah-Hartman
2023-06-12 18:07 ` Pavel Machek
2023-06-12 18:13 ` Greg Kroah-Hartman
2023-06-12 21:53 ` Chris Paterson
2023-06-13 0:47 ` Shuah Khan
2023-06-13 4:25 ` Bagas Sanjaya
2023-06-13 8:10 ` Naresh Kamboju
2023-06-13 8:39 ` Jon Hunter
2023-06-13 8:47 ` Conor Dooley [this message]
2023-06-13 9:45 ` ogasawara takeshi
2023-06-13 12:15 ` Sudip Mukherjee (Codethink)
2023-06-13 23:10 ` Guenter Roeck
2023-06-13 23:40 ` Ron Economos
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=20230613-curdle-varied-0e920e75d1d9@wendy \
--to=conor.dooley@microchip.com \
--cc=akpm@linux-foundation.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
all inboxes | Powered by JetHome®