From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
Cc: stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>,
mizhang@google.com, 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, Vegard Nossum <vegard.nossum@oracle.com>,
Darren Kenny <darren.kenny@oracle.com>
Subject: Re: [PATCH 5.15 000/128] 5.15.138-rc1 review
Date: Tue, 7 Nov 2023 21:21:33 +0100 [thread overview]
Message-ID: <2023110717-saddlebag-reflected-ed93@gregkh> (raw)
In-Reply-To: <2665d8bc-111c-45ca-a473-b1c892867e9c@oracle.com>
On Mon, Nov 06, 2023 at 08:24:43PM +0530, Harshit Mogalapalli wrote:
> Hello Greg,
>
> On 06/11/23 6:32 pm, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.138 release.
> > There are 128 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 Wed, 08 Nov 2023 13:02:46 +0000.
> > Anything received after that time might be too late.
> >
>
> I am seeing a build failure with perf:
>
> tools/perf/util/evlist.c: In function evlist__add_aux_dummy:
> tools/perf/util/evlist.c:266:31: error: implicit declaration of function
> evlist__dummy_event; did you mean evlist__add_sb_event’?
> [-Werror=implicit-function-declaration]
> 266 | struct evsel *evsel = evlist__dummy_event(evlist);
> | ^~~~~~~~~~~~~~~~~~~
> | evlist__add_sb_event
>
>
> I think we should drop these three commits:
>
> 20a5799cae7dc perf evlist: Avoid frequency mode for the dummy event
> 7de783c81c7e7 perf tools: Get rid of evlist__add_on_all_cpus()
> 141ce9207068e perf evlist: Add evlist__add_dummy_on_all_cpus()
Thanks, I've dropped all of these from 5.15.y and 5.10.y now.
greg k-h
next prev parent reply other threads:[~2023-11-07 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 13:02 [PATCH 5.15 000/128] 5.15.138-rc1 review Greg Kroah-Hartman
2023-11-06 14:54 ` Harshit Mogalapalli
2023-11-06 17:08 ` Allen Pais
2023-11-06 17:42 ` Florian Fainelli
2023-11-07 15:33 ` Harshit Mogalapalli
2023-11-07 20:21 ` Greg Kroah-Hartman [this message]
2023-11-06 17:23 ` SeongJae Park
2023-11-07 8:56 ` Ron Economos
2023-11-07 11:43 ` Jon Hunter
2023-11-07 15:37 ` Shuah Khan
2023-11-07 17:15 ` Ricardo B. Marliere
2023-11-07 17:58 ` Naresh Kamboju
2023-11-07 18:55 ` Guenter Roeck
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=2023110717-saddlebag-reflected-ed93@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=conor@kernel.org \
--cc=darren.kenny@oracle.com \
--cc=f.fainelli@gmail.com \
--cc=harshit.m.mogalapalli@oracle.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkft-triage@lists.linaro.org \
--cc=mizhang@google.com \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=vegard.nossum@oracle.com \
/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