mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, 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@nabladev.com,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, rwarsow@gmx.de, conor@kernel.org,
	hargar@microsoft.com, broonie@kernel.org, achill@achill.org,
	sr@sladewatkins.com, Herve Codina <herve.codina@bootlin.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Kalle Niemi <kaleposti@gmail.com>
Subject: Re: [PATCH 6.12 0000/1202] 6.12.97-rc2 review
Date: Mon, 14 Sep 2026 11:13:54 +0300	[thread overview]
Message-ID: <d601964b-e437-4990-bbdd-0337bba49102@gmail.com> (raw)
In-Reply-To: <20260722142834.868902312@linuxfoundation.org>

On 22/07/2026 17:31, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.12.97 release.
> There are 1202 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 Fri, 24 Jul 2026 14:26:57 +0000.
> Anything received after that time might be too late.

Oh, time flies. :) Well, statement understood...

... Still, even though I know I am late - I am seeing our tests failing 
for stable 6.12.x. Other stables as well as mainline releases and 
linux-next are passing.

The actual failure seems identical to one discussed here:
https://lore.kernel.org/all/072dde7c-a53c-4525-83ac-57ea38edc0b5@gmail.com/

I believe above was fixed by Herve.

Bisecting stable points the:

> Saravana Kannan <saravanak@google.com>
>      Revert "treewide: Fix probing of devices in DT overlays"
which matches the issue in discussion.

Maybe the 6.12 stable is missing Herve's latest fix(es)?

As explained in original report, the issue is seen with our out-of-tree 
device-tree overlay stuff. I have no idea if there is any in-tree stuff 
impacted but I guess the overlay stuff Geert has in Renesas tree might 
also be impacted - if it was based on 6.12.

I believe there is an "existing easy fix", in a form of a patch which is 
already applied to other stables. Unfortunately I lost track of the 
relevant fixes during the discussion so I can't point the relevant one.

Herve, do you happen to know what might be missing?

I suppose this would be worth fixing because 6.12 is expected to be 
alive for a while.


Ps. I am not sure if this mail thread is the right place to report 
issues _after_ the stable is out? I'd appreciate a pointer if there is a 
better place (for the future reports).

Yours,
	-- Matti

-- 
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~

      parent reply	other threads:[~2026-09-14  8:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 14:31 Greg Kroah-Hartman
2026-07-22 16:54 ` Brett A C Sheffield
2026-07-22 18:27 ` Pavel Machek
2026-07-22 18:40 ` Florian Fainelli
2026-07-23  8:01 ` Peter Schneider
2026-07-23  8:41 ` Shung-Hsi Yu
2026-07-23 11:24 ` Miguel Ojeda
2026-07-23 15:17 ` Mark Brown
2026-07-24  6:19   ` Greg Kroah-Hartman
2026-07-24  7:38     ` Thorsten Leemhuis
2026-07-24 12:55     ` Mark Brown
2026-09-14  8:13 ` Matti Vaittinen [this message]

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=d601964b-e437-4990-bbdd-0337bba49102@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --cc=herve.codina@bootlin.com \
    --cc=jonathanh@nvidia.com \
    --cc=kaleposti@gmail.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@nabladev.com \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=sr@sladewatkins.com \
    --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

all inboxes | Powered by JetHome®