From: Ben Hutchings <ben@decadent.org.uk>
To: Ian Rogers <irogers@google.com>
Cc: debian-kernel@lists.debian.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
waldi@debian.org,
linux-perf-users <linux-perf-users@vger.kernel.org>,
Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>
Subject: Re: Getting the latest and greatest Linux perf features on every Debian kernel
Date: Fri, 13 Jan 2023 23:06:55 +0100 [thread overview]
Message-ID: <0b1c5f9af241327786a996a3ddd61602b5a15987.camel@decadent.org.uk> (raw)
In-Reply-To: <CAP-5=fUcc-SmxqgNCnqNAc=adGdzK31eQtv8XKQLt8v4EtLguQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 703 bytes --]
On Mon, 2023-01-09 at 17:32 -0800, Ian Rogers wrote:
[...]
> Thanks again Ben! With the releases, the plan is to follow the kernel
> releases? We could potentially be more aggressive with the perf tool
> given its backward compatibility. That would benefit people using
> older kernels who want the latest perf tool bug fixes and features.
>
Yes, we continue to build perf from the same source package as our
kernel images. Users of a stable release can still install newer
versions of perf and/or the kernel from the corresponding -backports
suite without upgrading everything elese.
Ben.
--
Ben Hutchings
The program is absolutely right; therefore, the computer must be wrong.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-13 22:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 6:34 Getting the latest and greatest Linux perf features on every Debian kernel Ian Rogers
2021-11-12 14:39 ` Arnaldo Carvalho de Melo
2021-11-22 2:18 ` Ian Rogers
2021-11-22 12:54 ` Moessbauer, Felix
2021-11-22 16:57 ` Ian Rogers
2021-11-23 7:46 ` Moessbauer, Felix
2022-01-09 23:54 ` Ben Hutchings
2022-01-10 18:44 ` Arnaldo Carvalho de Melo
2022-12-23 1:43 ` Ian Rogers
2022-12-25 11:51 ` Andi Kleen
2022-12-26 16:12 ` Moessbauer, Felix
2022-12-26 19:15 ` Ben Hutchings
2023-01-10 1:32 ` Ian Rogers
2023-01-13 22:06 ` Ben Hutchings [this message]
2022-01-09 23:41 ` Ben Hutchings
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=0b1c5f9af241327786a996a3ddd61602b5a15987.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=acme@kernel.org \
--cc=debian-kernel@lists.debian.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=waldi@debian.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 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.