From: Namhyung Kim <namhyung@kernel.org>
To: Milian Wolff <milian.wolff@kdab.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: perf FTBFS due to -Werror with gcc 14.1.1
Date: Tue, 4 Jun 2024 15:43:42 -0700 [thread overview]
Message-ID: <Zl-YnpW2BUcr-M8c@google.com> (raw)
In-Reply-To: <4396113.DFci0H2nWq@milian-workstation>
Hello,
On Tue, Jun 04, 2024 at 09:58:20PM +0200, Milian Wolff wrote:
> On Dienstag, 4. Juni 2024 15:45:52 MESZ Arnaldo Carvalho de Melo wrote:
> > On Tue, Jun 04, 2024 at 01:40:19PM +0200, Milian Wolff wrote:
> > > Hey all,
> > >
> > > I cannot build the acme perf/core branch on Arch anymore with gcc 14.1.1
> > > and
> > perf/core isn't being updated for quite a while, we nowadays update just
> > the perf-tools (current merge window) and perf-tools-next (next merge
> > window/devel).
> >
> > Also I still keep my tree uptodate when I'm updating those branches, but
> > nowadays the trees/branches to be used are:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools.git
> > perf-tools
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools-next.git
> > perf-tools-next
> >
> > As Namhyung Kim is a perf tools co-maintainer and keeps one of these
> > trees+branch while I keep the other.
> >
> > Right now I'm taking care of perf-tools while Namhyung is managing
> > perf-tools.next.
>
> Ah indeed that's it, thank you!
>
> Which one of the two would you recommend for interested parties that want to
> keep track of perf tools development, i.e. what was perf/core?
The perf-tools-next is for new development (previously perf/core) and the
perf-tools is for fixes in the current cycles (previously perf/urgent).
Thanks,
Namhyung
prev parent reply other threads:[~2024-06-04 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 11:40 perf FTBFS due to -Werror with gcc 14.1.1 Milian Wolff
2024-06-04 13:45 ` Arnaldo Carvalho de Melo
2024-06-04 19:58 ` Milian Wolff
2024-06-04 22:43 ` Namhyung Kim [this message]
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=Zl-YnpW2BUcr-M8c@google.com \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=milian.wolff@kdab.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.