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>, <conor@kernel.org>, <allen.lkml@gmail.com>
Subject: Re: [PATCH 6.1 000/194] 6.1.68-rc1 review
Date: Tue, 12 Dec 2023 14:02:29 +0000 [thread overview]
Message-ID: <20231212-entertain-handshake-faad98b5651d@wendy> (raw)
In-Reply-To: <20231211182036.606660304@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 371 bytes --]
On Mon, Dec 11, 2023 at 07:19:50PM +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.68 release.
> There are 194 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>
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-12 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 18:19 Greg Kroah-Hartman
2023-12-11 21:15 ` Florian Fainelli
2023-12-12 0:26 ` Kelsey Steele
2023-12-12 13:21 ` Naresh Kamboju
2023-12-12 14:02 ` Conor Dooley [this message]
2023-12-12 16:12 ` Shuah Khan
2023-12-12 17:34 ` Guenter Roeck
2023-12-12 19:08 ` Pavel Machek
2023-12-12 20:08 ` RTL8152_INACCESSIBLE was " Pavel Machek
2023-12-12 20:48 ` Guenter Roeck
2023-12-13 7:52 ` Pavel Machek
2023-12-13 8:50 ` Greg Kroah-Hartman
2023-12-13 15:16 ` Doug Anderson
2023-12-13 17:37 ` Greg Kroah-Hartman
2023-12-13 18:17 ` Doug Anderson
2023-12-12 21:57 ` Ron Economos
2023-12-12 22:21 ` Jon Hunter
2023-12-12 22:23 ` SeongJae Park
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=20231212-entertain-handshake-faad98b5651d@wendy \
--to=conor.dooley@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--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
all inboxes | Powered by JetHome®