The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: Sasha Levin <sashal@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@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,
	Florian Fainelli <f.fainelli@gmail.com>
Subject: Re: [PATCH 7.1 0000/2077] 7.1.5-rc1 review
Date: Wed, 22 Jul 2026 12:43:16 -0400	[thread overview]
Message-ID: <20260722113506.rc-reply-0006@kernel.org> (raw)
In-Reply-To: <b7e241f0-2604-4609-ac21-483b95757e10@gmail.com>

On Tue, Jul 21, 2026 at 10:54:18AM -0700, Florian Fainelli wrote:
> builtin-sched.c:1196:34: error: 'struct perf_sample' has no member named
> 'file_offset'
>
> which is due to 6018a2a9ff1baa45426f7a52f8ec4f7d32fedfce ("perf sched:
> Replace BUG_ON on invalid CPU with graceful skip"), we need to backport
> a490187f22b4bfae7ef752edbe3fb13017ca11c ("perf sample: Add file_offset
> field to struct perf_sample")

Greg has queued 7a490187f22b for 7.1 (ordered right before the
perf-sched patch), so this is resolved for -rc2.

The other two perf build errors reported in this thread are covered as
well: the libdw.c inline_node__clear_frames() failure is fixed by
674dea094ef6 ("perf srcline: Introduce inline_node__clear_frames()"),
which is now also queued.

Thorsten's third error ('evsel' undeclared in
perf_session__deliver_event at util/session.c) doesn't apply to the
queue itself: that code block comes from upstream a2e59fb79f449f
("perf session: Bound nr_cpus_avail and validate sample CPU"), which
isn't queued for 7.1. His local cherry-pick of 7a490187f22b pulled in
that surrounding context without the evsel declaration; the backport
in the queue doesn't carry it. I verified the current queue's
perf_session__deliver_event has no evsel reference and that perf from
the current 7.1 queue builds cleanly, so -rc2 should be good.

-- 
Thanks,
Sasha

  parent reply	other threads:[~2026-07-22 16:43 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 14:54 [PATCH 7.1 0000/2077] 7.1.5-rc1 review Greg Kroah-Hartman
2026-07-21 14:57 ` [PATCH 7.1 0184/2077] uaccess: fix ignored_trailing logic in copy_struct_to_user() Greg Kroah-Hartman
2026-07-21 14:57 ` [PATCH 7.1 0185/2077] sockptr: fix usize check in copy_struct_from_sockptr() for user pointers Greg Kroah-Hartman
2026-07-21 15:14 ` [PATCH 7.1 1190/2077] rtc: ds1307: handle oscillator stop flag for ds1337/ds1339/ds3231 Greg Kroah-Hartman
2026-07-21 15:18 ` [PATCH 7.1 1416/2077] arm64/mm: Optimize TLB flush in unmap_hotplug_[pmd|pud]_range() Greg Kroah-Hartman
2026-07-21 17:54 ` [PATCH 7.1 0000/2077] 7.1.5-rc1 review Florian Fainelli
2026-07-22  4:23   ` Thorsten Leemhuis
2026-07-22 12:20     ` Greg Kroah-Hartman
2026-07-22 16:43   ` Sasha Levin [this message]
2026-07-21 20:21 ` Ronald Warsow
2026-07-21 22:21 ` Brett A C Sheffield
2026-07-22  4:42 ` Peter Schneider
2026-07-22 10:32 ` Ron Economos
2026-07-22 12:40 ` Takeshi Ogasawara
     [not found] ` <4dbf52af-61a2-4767-8c85-b358cc157812@rnnvmail201.nvidia.com>
2026-07-22 13:14   ` Jon Hunter
2026-07-22 16:56 ` Shuah Khan
2026-07-22 17:47 ` 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=20260722113506.rc-reply-0006@kernel.org \
    --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