Archive-only list for patches
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	chris.paterson2@renesas.com
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,
	conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org,
	Gabriel Krisman Bertazi <krisman@suse.de>
Subject: Re: [PATCH 6.11 000/212] 6.11.4-rc2 review
Date: Wed, 16 Oct 2024 11:33:18 +0200	[thread overview]
Message-ID: <Zw+IXqfj5IA1KXj+@duo.ucw.cz> (raw)
In-Reply-To: <20241015112329.364617631@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 2632 bytes --]

Hi!

> This is the start of the stable review cycle for the 6.11.4 release.
> There are 212 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.

What went wrong with the release announcement? It has patch appended at the end.

https://lore.kernel.org/all/20241015112329.364617631@linuxfoundation.org/

According to our testing, it breaks boot on de0-nano-soc.

https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/1497863060

Same problem with 6.6. Quoting from Chris Paterson:

# Interesting.
# The de0-nano-soc device seems to be working from a LAVA point of view, it's just
# the kernel that isn't loading.

# If you look at the job history [0] for one of the de0-nano-soc devices you can
# see that it's booting okay for various kernels, but not all of them.
# multi_v7_defconfig seemed to boot okay with 6.12.0-rc2_d3d155669 [1], but not
# since 6.12.0-rc3_6485cf5ea [2].

# [0] https://lava.ciplatform.org/scheduler/device/de0-nano-soc-03?recent_search=&recent_length=100#recent_
# [1] https://lava.ciplatform.org/scheduler/job/1205245
# [2] https://lava.ciplatform.org/scheduler/job/1206169

Quick test showed that 5.10-cip kernel still works on that target, so
it seems to be real issue.

Best regards,
								Pavel

> 
> 
> From gregkh@linuxfoundation.org Tue Oct 15 13:23:29 2024
> Message-ID: <20241015112329.430115421@linuxfoundation.org>
> User-Agent: quilt/0.67
> Date: Tue, 15 Oct 2024 13:23:30 +0200
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> To: stable@vger.kernel.org
> Cc: 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, conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org,
>  Gabriel Krisman Bertazi <krisman@suse.de>
> X-stable: review
> X-Patchwork-Hint: ignore
> Subject: [PATCH 6.11 001/212] unicode: Dont special case ignorable code points
> MIME-Version: 1.0
> 
> 6.11-stable review patch.  If anyone has any objections, please let me know.
> 
> ------------------
> 
> From: Gabriel Krisman Bertazi <krisman@suse.de>
> 
> commit 5c26d2f1d3f5e4be3e196526bead29ecb139cf91 upstream.

-- 
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 --]

  parent reply	other threads:[~2024-10-16  9:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-15 11:25 [PATCH 6.11 000/212] 6.11.4-rc2 review Greg Kroah-Hartman
2024-10-15 15:18 ` Ron Economos
2024-10-16  7:40   ` Naresh Kamboju
2024-10-15 17:55 ` Florian Fainelli
2024-10-16  7:50 ` Kexy Biscuit
2024-10-16  9:33 ` Pavel Machek [this message]
2024-10-17  7:34   ` Pavel Machek
2024-10-16 10:02 ` Jon Hunter
2024-10-17 13:30 ` Muhammad Usama Anjum

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=Zw+IXqfj5IA1KXj+@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=akpm@linux-foundation.org \
    --cc=allen.lkml@gmail.com \
    --cc=broonie@kernel.org \
    --cc=chris.paterson2@renesas.com \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=krisman@suse.de \
    --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=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