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.7 000/707] 6.7.11-rc2 review
Date: Mon, 25 Mar 2024 20:07:22 +0100 [thread overview]
Message-ID: <ZgHLahR2Do2nweDm@duo.ucw.cz> (raw)
In-Reply-To: <20240325120003.1767691-1-sashal@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 760 bytes --]
Hi!
> This is the start of the stable review cycle for the 6.7.11 release.
> There are 707 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.
We see failures on 6.8
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1226528038
and 6.7
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1226365165
These are ok:
Linux 6.6.23-rc2 (e9d47628c833)
Linux 5.4.273-rc2 (600a0ba48796)
Linux 5.15.153-rc2 (d978081b2581)

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:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 12:00 [PATCH 6.7 000/707] 6.7.11-rc2 review Sasha Levin
2024-03-25 17:43 ` Daniel Díaz
2024-03-25 18:14 ` Sami Tolvanen
2024-03-25 19:47 ` Daniel Díaz
2024-03-26 11:23 ` Sasha Levin
2024-03-25 17:57 ` SeongJae Park
2024-03-25 18:22 ` Naresh Kamboju
2024-03-25 19:07 ` Pavel Machek [this message]
2024-03-25 20:05 ` Justin Forbes
2024-03-25 20:39 ` Florian Fainelli
2024-03-26 2:09 ` Bagas Sanjaya
2024-03-26 9:04 ` Ron Economos
2024-03-26 16:16 ` Mark Brown
2024-03-26 17:28 ` Greg KH
2024-03-26 17:35 ` Mark Brown
2024-03-26 17:00 ` Shuah Khan
2024-03-26 19:52 ` Conor Dooley
2024-03-26 20:48 ` Shreeya Patel
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=ZgHLahR2Do2nweDm@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