mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Salvatore Bonaccorso <carnil@debian.org>
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,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
	achill@achill.org
Subject: Re: [PATCH 6.16 000/627] 6.16.1-rc1 review
Date: Thu, 14 Aug 2025 06:01:02 +0200	[thread overview]
Message-ID: <aJ1ffsxetEzx9HKC@lorien.valinor.li> (raw)
In-Reply-To: <20250812173419.303046420@linuxfoundation.org>

Hi,

On Tue, Aug 12, 2025 at 07:24:55PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.16.1 release.
> There are 627 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 Thu, 14 Aug 2025 17:32:40 +0000.
> Anything received after that time might be too late.

While testing I noticed two new warnings compared to previous tests
with stable series:

[    0.000000] x86 CPU feature dependency check failure: CPU0 has '18*32+31' enabled but '18*32+26' disabled. Kernel might be fine, but no guarantees.
[...]
[   60.281912] sched: DL replenish lagged too much

Need to investigate more.

Regards,
Salvatore

  parent reply	other threads:[~2025-08-14  4:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-12 17:24 Greg Kroah-Hartman
2025-08-12 19:48 ` Brett A C Sheffield
2025-08-12 21:56 ` Florian Fainelli
2025-08-13  6:12 ` Peter Schneider
2025-08-13 11:39 ` Frank Scheiner
2025-08-13 11:40 ` Takeshi Ogasawara
2025-08-13 12:16 ` Naresh Kamboju
2025-08-13 12:50   ` Greg Kroah-Hartman
2025-08-13 14:31     ` Naresh Kamboju
2025-08-13 14:53       ` Greg Kroah-Hartman
2025-08-13 15:58         ` Dan Carpenter
2025-08-14  1:27         ` Zhang Yi
2025-08-14 15:30           ` Greg Kroah-Hartman
2025-08-14 20:19     ` Namhyung Kim
2025-08-15  5:33       ` Greg Kroah-Hartman
2025-08-15 16:24         ` Namhyung Kim
2025-08-13 12:51   ` Mark Brown
2025-08-13 13:41     ` Naresh Kamboju
2025-08-14 15:35       ` Greg Kroah-Hartman
2025-08-13 13:56 ` Mark Brown
2025-08-13 15:05 ` Shuah Khan
2025-08-13 15:48 ` Jon Hunter
2025-08-13 21:26 ` Ron Economos
2025-08-14  4:01 ` Salvatore Bonaccorso [this message]
2025-08-14 10:25 ` Christian Heusel
2025-08-14 14:57 ` Miguel Ojeda

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=aJ1ffsxetEzx9HKC@lorien.valinor.li \
    --to=carnil@debian.org \
    --cc=achill@achill.org \
    --cc=akpm@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=conor@kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hargar@microsoft.com \
    --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=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®