From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
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, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
hargar@microsoft.com, broonie@kernel.org
Subject: Re: [PATCH 6.6 000/109] 6.6.67-rc1 review
Date: Thu, 19 Dec 2024 17:05:27 +0100 [thread overview]
Message-ID: <2024121921-employed-crabmeat-1b21@gregkh> (raw)
In-Reply-To: <6c36f396-fb6c-4cbe-86e2-39b3ce85ffd3@gmail.com>
On Tue, Dec 17, 2024 at 12:00:51PM -0800, Florian Fainelli wrote:
> On 12/17/24 09:06, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.6.67 release.
> > There are 109 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, 19 Dec 2024 17:05:03 +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.6.67-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.6.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> perf fails to build with:
>
> evlist.c: In function '__perf_evlist__propagate_maps':
> evlist.c:55:21: error: implicit declaration of function
> 'perf_cpu_map__is_empty'; did you mean 'perf_cpu_map__empty'?
> [-Werror=implicit-function-declaration]
> 55 | if (perf_cpu_map__is_empty(evsel->cpus)) {
> | ^~~~~~~~~~~~~~~~~~~~~~
> | perf_cpu_map__empty
> evlist.c:55:21: error: nested extern declaration of 'perf_cpu_map__is_empty'
> [-Werror=nested-externs]
> cc1: all warnings being treated as errors
> make[6]: *** [/local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/build/Makefile.build:98: /local/users/fainelli/buildroot/output/arm/build/linux-custom/tools/perf/libperf/evlist.o]
> Error 1
>
> this is caused by 74d444cca1eb616912c3ffe4b8a060a7bb192618 ("libperf:
> evlist: Fix --cpu argument on hybrid platform")
Now dropped, thanks.
greg k-h
next prev parent reply other threads:[~2024-12-19 16:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-17 17:06 [PATCH 6.6 000/109] 6.6.67-rc1 review Greg Kroah-Hartman
2024-12-17 20:00 ` Florian Fainelli
2024-12-19 16:05 ` Greg Kroah-Hartman [this message]
2024-12-17 23:00 ` Shuah Khan
2024-12-18 5:49 ` Harshit Mogalapalli
2024-12-19 16:05 ` Greg Kroah-Hartman
2024-12-18 6:49 ` Ron Economos
2024-12-18 12:11 ` Peter Schneider
2024-12-18 12:37 ` Mark Brown
2024-12-18 14:13 ` Naresh Kamboju
2024-12-18 17:23 ` Jon Hunter
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=2024121921-employed-crabmeat-1b21@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=f.fainelli@gmail.com \
--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