From: Florian Fainelli <f.fainelli@gmail.com>
To: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>,
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@denx.de,
jonathanh@nvidia.com, sudipm.mukherjee@gmail.com,
srw@sladewatkins.net, rwarsow@gmx.de, conor@kernel.org,
allen.lkml@gmail.com, broonie@kernel.org,
Vegard Nossum <vegard.nossum@oracle.com>,
Darren Kenny <darren.kenny@oracle.com>
Subject: Re: [PATCH 6.6 000/386] 6.6.55-rc1 review
Date: Tue, 8 Oct 2024 10:55:05 -0700 [thread overview]
Message-ID: <f7bbebca-4da4-4270-ba6c-659a4c40b430@gmail.com> (raw)
In-Reply-To: <894e27c0-c1e8-476d-ae16-11ab65853d1f@oracle.com>
On 10/8/24 07:58, Harshit Mogalapalli wrote:
> Hi Greg,
>
> On 08/10/24 17:34, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.6.55 release.
>> There are 386 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, 10 Oct 2024 11:55:15 +0000.
>> Anything received after that time might be too late.
>>
> ...
>
>
>> Ian Rogers <irogers@google.com>
>> perf callchain: Fix stitch LBR memory leaks
>>
>
> This patch is causing build failures for tools/perf/
Yes, same here.
>
> util/machine.c: In function 'save_lbr_cursor_node':
> util/machine.c:2540:9: error: implicit declaration of function
> 'map_symbol__exit'; did you mean 'symbol__exit'? [-Werror=implicit-
> function-declaration]
> 2540 | map_symbol__exit(&lbr_stitch->prev_lbr_cursor[idx].ms);
> | ^~~~~~~~~~~~~~~~
> | symbol__exit
> ...
>
> util/thread.c: In function 'thread__free_stitch_list':
> util/thread.c:481:17: error: implicit declaration of function
> 'map_symbol__exit'; did you mean 'symbol__exit'? [-Werror=implicit-
> function-declaration]
> 481 | map_symbol__exit(&pos->cursor.ms);
> | ^~~~~~~~~~~~~~~~
> | symbol__exit
>
>
>
> Thanks,
> Harshit
--
Florian
next prev parent reply other threads:[~2024-10-08 17:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 12:04 Greg Kroah-Hartman
2024-10-08 14:58 ` Harshit Mogalapalli
2024-10-08 17:55 ` Florian Fainelli [this message]
2024-10-10 10:16 ` Greg Kroah-Hartman
2024-10-08 17:05 ` Peter Schneider
2024-10-08 17:29 ` Mark Brown
2024-10-08 21:59 ` Shuah Khan
2024-10-09 6:24 ` Naresh Kamboju
2024-10-09 6:49 ` Harshit Mogalapalli
2024-10-09 12:48 ` Takeshi Ogasawara
2024-10-09 14:58 ` Jon Hunter
2024-10-10 0:14 ` Ron Economos
2024-10-10 9:00 ` Muhammad Usama Anjum
2024-10-10 11:13 ` 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=f7bbebca-4da4-4270-ba6c-659a4c40b430@gmail.com \
--to=f.fainelli@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=darren.kenny@oracle.com \
--cc=gregkh@linuxfoundation.org \
--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=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 \
--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
all inboxes | Powered by JetHome®