From: Florian Fainelli <f.fainelli@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, 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.18 0000/1611] 6.18.40-rc1 review
Date: Tue, 21 Jul 2026 10:48:11 -0700 [thread overview]
Message-ID: <8869a0f4-8e26-4f83-b258-f633a6eb6da3@gmail.com> (raw)
In-Reply-To: <20260721152514.750365251@linuxfoundation.org>
On 7/21/26 08:01, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.18.40 release.
> There are 1611 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, 23 Jul 2026 15:23:00 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v6.x/stable-review/patch-6.18.40-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.18.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
perf fails to build with:
util/arm-spe.c: In function 'arm_spe__inject_event':
util/arm-spe.c:472:37: error: 'struct perf_sample' has no member named
'evsel'
472 | struct evsel *evsel = sample->evsel;
| ^~
due to commit ca625699a8d5ddea7213231f090dab1e0ec0380c ("perf event: Fix
size of synthesized sample with branch stacks"), it looks like we need
to backport aeae075a0352eb6ab363fb1910f209eaa296a175 ("perf sample: Add
evsel to struct perf_sample")
--
Florian
next prev parent reply other threads:[~2026-07-21 17:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 15:01 Greg Kroah-Hartman
2026-07-21 15:04 ` [PATCH 6.18 0134/1611] uaccess: fix ignored_trailing logic in copy_struct_to_user() Greg Kroah-Hartman
2026-07-21 15:16 ` [PATCH 6.18 0875/1611] rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231 Greg Kroah-Hartman
2026-07-21 15:19 ` [PATCH 6.18 1031/1611] arm64/mm: Optimize TLB flush in unmap_hotplug_[pmd|pud]_range() Greg Kroah-Hartman
2026-07-21 15:27 ` [PATCH 6.18 1547/1611] cifs: SMB1 split: Rename cifstransport.c Greg Kroah-Hartman
2026-07-21 15:27 ` [PATCH 6.18 1548/1611] cifs: SMB1 split: Add some #includes Greg Kroah-Hartman
2026-07-21 17:48 ` Florian Fainelli [this message]
2026-07-22 12:14 ` [PATCH 6.18 0000/1611] 6.18.40-rc1 review Greg Kroah-Hartman
2026-07-21 22:21 ` Brett A C Sheffield
2026-07-22 4:28 ` Peter Schneider
2026-07-22 5:15 ` Wentao Guan
2026-07-22 10:40 ` Ron Economos
2026-07-22 16:57 ` Shuah Khan
2026-07-22 17:46 ` Pavel Machek
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=8869a0f4-8e26-4f83-b258-f633a6eb6da3@gmail.com \
--to=f.fainelli@gmail.com \
--cc=achill@achill.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--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
all inboxes | Powered by JetHome®