linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Ian Rogers <irogers@google.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	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: Sun, 25 Dec 2022 03:51:45 -0800	[thread overview]
Message-ID: <874jtjem5q.fsf@linux.intel.com> (raw)
In-Reply-To: <CAP-5=fUzHV765DqcTZpqCKC1Ve1H91tUfoxQE7Z2KcK5yq021A@mail.gmail.com> (Ian Rogers's message of "Thu, 22 Dec 2022 17:43:56 -0800")

Ian Rogers <irogers@google.com> writes:

> So I wanted to say a BIG thanks to Ben as I see in the 5.16 changelog
> that the perf wrapper script for Debian is now gone!
> https://metadata.ftp-master.debian.org/changelogs//main/l/linux/linux_6.1~rc8-1~exp1_changelog

Halleluja! This wrapper literally is the singlest biggest usability problem with
perf with real users. Hopefully that change gets picked up everywhere as
soon possible.

-Andi

  reply	other threads:[~2022-12-25 11:52 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 [this message]
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
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=874jtjem5q.fsf@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=ben@decadent.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).