mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	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, 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/244] 5.15.139-rc1 review
Date: Mon, 20 Nov 2023 00:22:25 +0530	[thread overview]
Message-ID: <62e2cf6e-57c6-479c-b2ce-16851968f4ac@oracle.com> (raw)
In-Reply-To: <ZVYf1VZ1xKQF23Qr@sashalap>

Hello Sasha and Greg,

On 16/11/23 7:27 pm, Sasha Levin wrote:
> On Thu, Nov 16, 2023 at 04:04:10PM +0530, Harshit Mogalapalli wrote:
>> Hi Greg,
>>
>> On 16/11/23 2:03 am, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 5.15.139 release.
>>> There are 244 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 Fri, 17 Nov 2023 20:34:45 +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/v5.x/stable-review/patch-5.15.139-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-5.15.y
>>> and the diffstat can be found below.
>>>
>>
>> As Florian pointed:
>>
>> I am also seeing build failure with perf, which is same as the 
>> previous cycle.
>>
>> BUILDSTDERR: util/evlist.c: In function 'evlist__add_aux_dummy':
>> BUILDSTDERR: util/evlist.c:266:31: error: implicit declaration of 
>> function 'evlist__dummy_event'; did you mean 'evlist__add_sb_event'? 
>> [-Werror=implicit-function-declaration]
>> BUILDSTDERR:   266 |         struct evsel *evsel = 
>> evlist__dummy_event(evlist);
>> BUILDSTDERR:       |                               ^~~~~~~~~~~~~~~~~~~
>> BUILDSTDERR:       |                               evlist__add_sb_event
>> BUILDSTDERR: util/evlist.c:266:31: error: initialization of 'struct 
>> evsel *' from 'int' makes pointer from integer without a cast 
>> [-Werror=int-conversion]
>>
>> I think we should drop:
>> 3dcc2e4843277 perf evlist: Avoid frequency mode for the dummy event
>> 4898cce349953 perf tools: Get rid of evlist__add_on_all_cpus()
>> a6157c9aa899a perf evlist: Add evlist__add_dummy_on_all_cpus()
> 
> Dropped, thanks!

I have reverted these locally and triggered tests on 5.15.139-rc1.

No problems seen on x86_64 and aarch64 with our testing.

Tested-by: Harshit Mogalapalli <harshit.m.mogalapalli@oracle.com>

Thanks,
Harshit
> 


  reply	other threads:[~2023-11-19 18:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15 20:33 Greg Kroah-Hartman
2023-11-15 22:29 ` SeongJae Park
2023-11-15 23:12 ` Florian Fainelli
2023-11-16 10:34 ` Harshit Mogalapalli
2023-11-16 13:57   ` Sasha Levin
2023-11-19 18:52     ` Harshit Mogalapalli [this message]
2023-11-16 18:20 ` Naresh Kamboju
2023-11-16 23:39 ` Guenter Roeck
2023-11-17 19:35   ` Allen Pais
2023-11-18  1:18 ` Ron Economos

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=62e2cf6e-57c6-479c-b2ce-16851968f4ac@oracle.com \
    --to=harshit.m.mogalapalli@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=conor@kernel.org \
    --cc=darren.kenny@oracle.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --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=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

all inboxes | Powered by JetHome®