From: Sasha Levin <sashal@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org,
gregkh@linuxfoundation.org, patches@lists.linux.dev,
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, sudipm.mukherjee@gmail.com, rwarsow@gmx.de,
conor@kernel.org, hargar@microsoft.com, broonie@kernel.org,
achill@achill.org, sr@sladewatkins.com
Subject: Re: [PATCH 6.19 000/311] 6.19.7-rc1 review
Date: Wed, 11 Mar 2026 19:18:17 -0400 [thread overview]
Message-ID: <abH4OYeVMctC3Cs-@laps> (raw)
In-Reply-To: <97a13d4f-e1ee-42f5-ab90-d6dc589ecefc@gmail.com>
On Wed, Mar 11, 2026 at 09:47:16AM -0700, Florian Fainelli wrote:
>
>
>On 3/10/2026 6:06 PM, Sasha Levin wrote:
>>On Tue, Mar 10, 2026 at 12:09:32PM -0700, Florian Fainelli wrote:
>>>On 3/10/26 04:05, Sasha Levin wrote:
>>>>
>>>>This is the start of the stable review cycle for the 6.19.7 release.
>>>>There are 311 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 Mar 12 11:04:16 AM UTC 2026.
>>>>Anything received after that time might be too late.
>>>>
>>>>The whole patch series can be found in one patch at:
>>>>
>>>>https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
>>>>stable-rc.git/rawdiff/?id=linux-6.19.y&id2=v6.19.6
>>>>or in the git tree and branch at:
>>>>
>>>>git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
>>>>stable-rc.git linux-6.19.y
>>>>and the diffstat can be found below.
>>>>
>>>>Thanks,
>>>>Sasha
>>>>
>>>>-------------
>>>perf fails to build the pmu-events for all of the freescale SoCs,
>>>I am not sure yet whether this is a build environment issue or a
>>>genuine perf build system failure:
>>
>>Could you try building with a revert of b56111d7a464 ("perf jevents: Handle
>>deleted JSONS in out of source builds") please?
>>
>
>Yes that does resolve it, thanks!
Awesome! Looking at the patch, it looks like it's a backport regression and
upstream should work just fine?
Assuming it's the case, I can revert this commit after the current release
cycle.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-03-11 23:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 11:05 [PATCH 6.19 000/311] 6.19.7-rc1 review Sasha Levin
2026-03-10 12:47 ` Brett A C Sheffield
2026-03-10 14:15 ` Ronald Warsow
2026-03-10 15:47 ` Dileep malepu
2026-03-10 15:52 ` Mark Brown
2026-03-10 18:55 ` Justin Forbes
2026-03-10 19:09 ` Florian Fainelli
2026-03-11 1:06 ` Sasha Levin
2026-03-11 16:47 ` Florian Fainelli
2026-03-11 23:18 ` Sasha Levin [this message]
2026-03-10 23:20 ` Ron Economos
2026-03-11 1:15 ` Peter Schneider
2026-03-11 2:46 ` Takeshi Ogasawara
2026-03-11 13:39 ` Luna Jernberg
2026-03-11 20:56 ` Shuah Khan
2026-03-11 21:11 ` Barry K. Nathan
2026-03-12 9:05 ` 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=abH4OYeVMctC3Cs-@laps \
--to=sashal@kernel.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@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