public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Rudi Heitbaum <rudi@heitbaum.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.3 000/694] 6.3.2-rc2 review
Date: Tue, 9 May 2023 08:06:58 +0000	[thread overview]
Message-ID: <20230509080658.GA152864@d6921c044a31> (raw)
In-Reply-To: <20230509030705.399628514@linuxfoundation.org>

On Tue, May 09, 2023 at 05:26:44AM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.3.2 release.
> There are 694 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, 11 May 2023 03:05:05 +0000.
> Anything received after that time might be too late.

Hi Greg,

6.3.2-rc2 tested.

Run tested on:
- Intel Alder Lake x86_64 (nuc12 i7-1260P)

In addition - build tested for:
- Allwinner A64
- Allwinner H3
- Allwinner H5
- NXP iMX6
- NXP iMX8
- Qualcomm Dragonboard
- Rockchip RK3288
- Rockchip RK3328
- Rockchip RK3399pro
- Samsung Exynos

Tested-by: Rudi Heitbaum <rudi@heitbaum.com>
--
Rudi

  reply	other threads:[~2023-05-09  8:08 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  3:26 [PATCH 6.3 000/694] 6.3.2-rc2 review Greg Kroah-Hartman
2023-05-09  8:06 ` Rudi Heitbaum [this message]
2023-05-09 13:10   ` Rudi Heitbaum
2023-05-09 13:56     ` Greg Kroah-Hartman
2023-05-09 14:58       ` Rudi Heitbaum
2023-05-09 19:30         ` Naresh Kamboju
2023-05-10  6:53           ` Rudi Heitbaum
2023-05-10  7:25         ` Greg Kroah-Hartman
2023-05-10  8:29           ` Rudi Heitbaum
2023-05-10  9:09             ` Greg Kroah-Hartman
2023-05-10 11:58               ` Rudi Heitbaum
2023-05-10 23:00                 ` Greg Kroah-Hartman
2023-05-11  8:30                   ` Rudi Heitbaum
2023-05-11 13:33                     ` Greg Kroah-Hartman
2023-05-11 14:19                     ` Linus Torvalds
2023-05-12  9:59                       ` Rudi Heitbaum
2023-05-09 12:25 ` Conor Dooley
2023-05-09 13:32 ` Bagas Sanjaya
2023-05-09 13:42 ` Chris Paterson
2023-05-09 18:57 ` Florian Fainelli
2023-05-09 19:16 ` Markus Reichelt
2023-05-09 19:24 ` Naresh Kamboju
2023-05-09 20:00 ` Guenter Roeck
2023-05-10  8:44 ` Sudip Mukherjee (Codethink)
  -- strict thread matches above, loose matches on Subject: below --
2023-05-09 10:23 Ronald Warsow

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=20230509080658.GA152864@d6921c044a31 \
    --to=rudi@heitbaum.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