mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vegard Nossum <vegard.nossum@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Harshit Mogalapalli <harshit.m.mogalapalli@oracle.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,
	Kamalesh Babulal <kamalesh.babulal@oracle.com>,
	pavel@denx.de, jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
	conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org,
	acme@redhat.com, namhyung@kernel.org, gpavithrasha@gmail.com,
	irogers@google.com, Darren Kenny <darren.kenny@oracle.com>
Subject: Re: [PATCH 5.15 000/402] 5.15.161-rc1 review
Date: Sat, 15 Jun 2024 20:09:11 +0200	[thread overview]
Message-ID: <596a3b8e-0d36-47bd-b3ac-68812506b307@oracle.com> (raw)
In-Reply-To: <2024061530-dress-powdery-c464@gregkh>


On 15/06/2024 13:05, Greg Kroah-Hartman wrote:
> On Fri, Jun 14, 2024 at 02:10:26PM +0530, Harshit Mogalapalli wrote:
>> I think building perf while adding perf patches would help us prevent from
>> running into this issue. cd tools/perf/ ; make -j$(nproc) all
> 
> Maybe, but I can't seem to build perf at all for quite a while, so I
> doubt that anyone really cares here, right?

We're building perf and it worked before these patches. It's part of our
kernel build and we do ship the result to customers. So we care :-)

>> We can choose one of the three ways to solve this :
>>
>> 1. Drop this patch and resolve conflicts in the next patch by keeping
>> pthread_mutex_*, but this might not help future backports.
> 
> Let me just drop all of the perf patches for now from 5.15 and then I'll
> take some tested backports if really needed.

Sounds good, thanks. We'll have a look at backports.

> Otherwise, why not just use perf from the latest 6.9 tree?

We have a build pipeline that's set up to build everything from the same
source tree and it's not really feasible to mix and match versions like
that -- besides, we don't want to jump from 5.15 to 6.9 for this stuff
any more than we do for the kernel itself.

Thanks,


Vegard

  reply	other threads:[~2024-06-15 18:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13 11:29 Greg Kroah-Hartman
2024-06-13 11:32 ` [PATCH 5.15 201/402] coresight: etm4x: Fix unbalanced pm_runtime_enable() Greg Kroah-Hartman
2024-06-13 16:48 ` [PATCH 5.15 000/402] 5.15.161-rc1 review SeongJae Park
2024-06-14  8:40 ` Harshit Mogalapalli
2024-06-15 11:05   ` Greg Kroah-Hartman
2024-06-15 18:09     ` Vegard Nossum [this message]
2024-06-16 12:55       ` Florian Fainelli
2024-06-14 12:19 ` Ron Economos
2024-06-14 14:15 ` Mark Brown
2024-06-14 17:03 ` Jon Hunter
2024-06-15  2:10 ` Shuah Khan
2024-06-15  6:46 ` Naresh Kamboju
2024-06-16 12:56 ` Florian Fainelli
2024-06-16 14:28   ` Greg Kroah-Hartman
2024-06-17  6:12     ` Harshit Mogalapalli

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=596a3b8e-0d36-47bd-b3ac-68812506b307@oracle.com \
    --to=vegard.nossum@oracle.com \
    --cc=acme@redhat.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=f.fainelli@gmail.com \
    --cc=gpavithrasha@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=harshit.m.mogalapalli@oracle.com \
    --cc=irogers@google.com \
    --cc=jonathanh@nvidia.com \
    --cc=kamalesh.babulal@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=namhyung@kernel.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

all inboxes | Powered by JetHome®