public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.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,
	srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 6.3 000/246] 6.3.3-rc1 review
Date: Tue, 16 May 2023 10:20:30 +0100	[thread overview]
Message-ID: <ZGNK3vxOsQXf3d9K@debian> (raw)
In-Reply-To: <20230515161722.610123835@linuxfoundation.org>

Hi Greg,

On Mon, May 15, 2023 at 06:23:32PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.3.3 release.
> There are 246 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.

Build test (gcc version 12.2.1 20230511):
mips: 52 configs -> no failure
arm: 71 configs -> no failure
arm64: 3 configs -> no failure
x86_64: 4 configs -> no failure
alpha allmodconfig -> no failure
csky allmodconfig -> no failure
powerpc allmodconfig -> no failure
riscv allmodconfig -> no failure
s390 allmodconfig -> no failure
xtensa allmodconfig -> no failure

Boot test:
x86_64: Booted on my test laptop. No regression.
x86_64: Booted on qemu. No regression. [1]
arm64: Booted on rpi4b (4GB model). No regression. [2]

[1]. https://openqa.qa.codethink.co.uk/tests/3539
[2]. https://openqa.qa.codethink.co.uk/tests/3540

Tested-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>

-- 
Regards
Sudip

  parent reply	other threads:[~2023-05-16  9:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 16:23 [PATCH 6.3 000/246] 6.3.3-rc1 review Greg Kroah-Hartman
2023-05-15 16:24 ` [PATCH 6.3 051/246] rxrpc: Fix hard call timeout units Greg Kroah-Hartman
2023-05-15 16:24 ` [PATCH 6.3 052/246] rxrpc: Make it so that a waiting process can be aborted Greg Kroah-Hartman
2023-05-15 16:24 ` [PATCH 6.3 053/246] rxrpc: Fix timeout of a call that hasnt yet been granted a channel Greg Kroah-Hartman
2023-05-15 20:14 ` [PATCH 6.3 000/246] 6.3.3-rc1 review Chris Paterson
2023-05-16  1:19 ` Shuah Khan
2023-05-16  3:33 ` Ron Economos
2023-05-16  9:03 ` Bagas Sanjaya
2023-05-16  9:20 ` Sudip Mukherjee (Codethink) [this message]
2023-05-16  9:51 ` Naresh Kamboju
2023-05-16 12:04 ` Justin Forbes
2023-05-16 12:26 ` Conor Dooley
2023-05-16 12:38 ` Rudi Heitbaum
2023-05-16 18:21 ` Markus Reichelt
2023-05-17  2:53 ` Guenter Roeck
2023-05-17  7:59 ` Jon Hunter
  -- strict thread matches above, loose matches on Subject: below --
2023-05-16 11:58 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=ZGNK3vxOsQXf3d9K@debian \
    --to=sudipm.mukherjee@gmail.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=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