linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Paterson <Chris.Paterson2@renesas.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Cc: "patches@lists.linux.dev" <patches@lists.linux.dev>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux@roeck-us.net" <linux@roeck-us.net>,
	"shuah@kernel.org" <shuah@kernel.org>,
	"patches@kernelci.org" <patches@kernelci.org>,
	"lkft-triage@lists.linaro.org" <lkft-triage@lists.linaro.org>,
	"pavel@denx.de" <pavel@denx.de>,
	"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"sudipm.mukherjee@gmail.com" <sudipm.mukherjee@gmail.com>,
	"srw@sladewatkins.net" <srw@sladewatkins.net>,
	"rwarsow@gmx.de" <rwarsow@gmx.de>,
	"conor@kernel.org" <conor@kernel.org>
Subject: RE: [PATCH 6.1 000/589] 6.1.39-rc3 review
Date: Tue, 18 Jul 2023 10:00:00 +0000	[thread overview]
Message-ID: <TY2PR01MB3788DB0982243F01F37AB34FB738A@TY2PR01MB3788.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20230717201547.359923764@linuxfoundation.org>

Hello Greg,

> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Sent: Monday, July 17, 2023 9:34 PM
> 
> This is the start of the stable review cycle for the 6.1.39 release.
> There are 589 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 Wed, 19 Jul 2023 20:14:46 +0000.
> Anything received after that time might be too late.

Thank you for the release!

CIP configurations built and booted okay with Linux 6.1.39-rc3 (ce7ec1011187):
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/934494457
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/commits/linux-6.1.y

Tested-by: Chris Paterson (CIP) <chris.paterson2@renesas.com>

Kind regards, Chris

  parent reply	other threads:[~2023-07-18 10:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17 20:34 [PATCH 6.1 000/589] 6.1.39-rc3 review Greg Kroah-Hartman
2023-07-17 22:39 ` Paul Barker
2023-07-17 22:50   ` Guenter Roeck
2023-07-20 17:50     ` Greg Kroah-Hartman
2023-07-17 23:33 ` ogasawara takeshi
2023-07-18  5:59 ` Bagas Sanjaya
2023-07-18  8:59 ` Jon Hunter
2023-07-18 10:00 ` Chris Paterson [this message]
2023-07-18 10:59 ` Ron Economos
2023-07-18 14:37 ` Naresh Kamboju
2023-07-18 16:55   ` Naresh Kamboju
2023-07-18 15:29 ` Guenter Roeck
2023-07-18 17:18 ` Joel Fernandes
2023-07-18 17:30 ` Allen Pais
2023-07-19  1:53 ` SeongJae Park
2023-07-19  9:38 ` Pavel Machek
2023-07-19 13:58   ` 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=TY2PR01MB3788DB0982243F01F37AB34FB738A@TY2PR01MB3788.jpnprd01.prod.outlook.com \
    --to=chris.paterson2@renesas.com \
    --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;
as well as URLs for NNTP newsgroup(s).