[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aABrSclgXsyzGo_g@x1>
Date: Wed, 16 Apr 2025 23:45:29 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: jiang.peng9@....com.cn
Cc: venkat88@...ux.ibm.com, atrajeev@...ux.ibm.com, namhyung@...nel.org,
linux-perf-users@...r.kernel.org, maddy@...ux.ibm.com,
mingo@...nel.org, linux-kernel@...r.kernel.org,
shao.mingyin@....com.cn, tglx@...utronix.de
Subject: Re: [mainline]tools/perf build warnings
On Thu, Apr 17, 2025 at 10:01:18AM +0800, jiang.peng9@....com.cn wrote:
> > I verified with perf-tools-next repo on both branches namely
> > tmp.perf-tools-next and perf-tools-next, and I think this warning got
> > recently introduced.
> > Git Bisect is pointing to acea9943271b62905033f2f8ca571cdd52d6ea7b as
> > first bad commit.
> Hi everyone,
> I apologize for the oversight. My commit
> (acea9943271b62905033f2f8ca571cdd52d6ea7b) updated
> include/vdso/unaligned.h but I forgot to sync it with
> tools/include/vdso/unaligned.h. I'll be more careful in the future to
> avoid such mistakes.
Hey, please take a look at:
tools/include/uapi/README
More importantly this paragraph:
"So its important not to touch the copies in tools/ when doing changes in
the original kernel headers, that will be done later, when
check-headers.sh inform about the change to the perf tools hackers."
Cheers,
- Arnaldo
Powered by blists - more mailing lists