From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, stable@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, florian.fainelli@broadcom.com,
pavel@denx.de
Subject: Re: [PATCH 6.1 000/444] 6.1.83-rc2 review
Date: Mon, 25 Mar 2024 20:04:29 +0100 [thread overview]
Message-ID: <ZgHKvRkywA4eBOEq@duo.ucw.cz> (raw)
In-Reply-To: <20240325115939.1766258-1-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
Hi!
> This is the start of the stable review cycle for the 6.1.83 release.
No, it is not. Start was at -rc1, this is -rc2. It would be nice to
mention it here, along with git hash so we could cross-check it
against our build systems.
CIP testing did not find any problems here:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-6.1.y
Tested-by: Pavel Machek (CIP) <pavel@denx.de>
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2024-03-25 19:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 11:59 [PATCH 6.1 000/444] 6.1.83-rc2 review Sasha Levin
2024-03-25 17:59 ` SeongJae Park
2024-03-25 18:48 ` Florian Fainelli
2024-03-25 19:04 ` Pavel Machek [this message]
2024-03-26 9:09 ` Ron Economos
2024-03-26 13:28 ` Naresh Kamboju
2024-03-26 17:08 ` Shuah Khan
2024-03-26 18:30 ` Shreeya Patel
2024-03-26 19:47 ` Mateusz Jończyk
2024-03-26 19:50 ` Conor Dooley
2024-03-27 1:49 ` Kelsey Steele
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=ZgHKvRkywA4eBOEq@duo.ucw.cz \
--to=pavel@denx.de \
--cc=akpm@linux-foundation.org \
--cc=florian.fainelli@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--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