From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: jiang.peng9@zte.com.cn
Cc: venkat88@linux.ibm.com, atrajeev@linux.ibm.com,
namhyung@kernel.org, linux-perf-users@vger.kernel.org,
maddy@linux.ibm.com, mingo@kernel.org,
linux-kernel@vger.kernel.org, shao.mingyin@zte.com.cn,
tglx@linutronix.de
Subject: Re: [mainline]tools/perf build warnings
Date: Wed, 16 Apr 2025 23:45:29 -0300 [thread overview]
Message-ID: <aABrSclgXsyzGo_g@x1> (raw)
In-Reply-To: <20250417100118733FrbRcKrZFI5AZsN2G6nyr@zte.com.cn>
On Thu, Apr 17, 2025 at 10:01:18AM +0800, jiang.peng9@zte.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
next prev parent reply other threads:[~2025-04-17 2:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 11:42 [mainline]tools/perf build warnings Venkat Rao Bagalkote
2025-04-16 13:11 ` Athira Rajeev
2025-04-16 14:03 ` Venkat Rao Bagalkote
2025-04-16 14:19 ` Venkat Rao Bagalkote
2025-04-16 14:34 ` Athira Rajeev
2025-04-16 17:16 ` Venkat Rao Bagalkote
2025-04-17 2:01 ` jiang.peng9
2025-04-17 2:45 ` Arnaldo Carvalho de Melo [this message]
2025-04-17 3:13 ` jiang.peng9
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=aABrSclgXsyzGo_g@x1 \
--to=acme@kernel.org \
--cc=atrajeev@linux.ibm.com \
--cc=jiang.peng9@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=shao.mingyin@zte.com.cn \
--cc=tglx@linutronix.de \
--cc=venkat88@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.