From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: sedat.dilek@gmail.com, Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
Namhyung Kim <namhyung@kernel.org>,
Quentin Monnet <quentin@isovalent.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [perf-tools] Build-error in tools/perf/util/annotate.c with LLVM-14
Date: Sun, 03 Jul 2022 14:46:56 -0300 [thread overview]
Message-ID: <F7CCD284-0DEF-444F-B58F-930678EC2644@gmail.com> (raw)
In-Reply-To: <20220703165448.7d2akxawzdvqigat@awork3.anarazel.de>
On July 3, 2022 1:54:48 PM GMT-03:00, Andres Freund <andres@anarazel.de> wrote:
>Hi,
>
>On 2022-07-03 10:54:45 -0300, Arnaldo Carvalho de Melo wrote:
>> That series should be split a bit further, so that the
>> new features test is in a separate patch, i.e. I don't process bpftool patches, but can process the feature test and the tools/perf part.
>
>Ok, will split it further. Should I do
>
>1) feature test
>2) introduce compat header header
>3) use feature test, use header in perf/
>4) use feature test, use header in bpf/
>
>Or should 3, 4 be split to separately introduce the feature test and use of
>the compat header?
I think 4 patches are ok,
- Arnaldo
>
>Greetings,
>
>Andres Freund
next prev parent reply other threads:[~2022-07-03 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 10:57 [perf-tools] Build-error in tools/perf/util/annotate.c with LLVM-14 Sedat Dilek
2022-07-03 11:03 ` Sedat Dilek
2022-07-03 11:06 ` Sedat Dilek
2022-07-03 11:54 ` Sedat Dilek
2022-07-03 13:54 ` Arnaldo Carvalho de Melo
2022-07-03 16:54 ` Andres Freund
2022-07-03 17:46 ` Arnaldo Carvalho de Melo [this message]
2022-07-03 20:32 ` Sedat Dilek
2022-07-03 16:51 ` Andres Freund
2022-07-03 20:40 ` Sedat Dilek
2022-07-03 21:31 ` Andres Freund
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=F7CCD284-0DEF-444F-B58F-930678EC2644@gmail.com \
--to=arnaldo.melo@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andres@anarazel.de \
--cc=bpf@vger.kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=quentin@isovalent.com \
--cc=sedat.dilek@gmail.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