mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Akemi Yagi <toracat@elrepo.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Ian Rogers <irogers@google.com>, Alan Bartlett <ajb@elrepo.org>,
	Leo Yan <leo.yan@linaro.org>, Ingo Molnar <mingo@redhat.com>,
	linux-perf-users@vger.kernel.org, ElRepo <contact@elrepo.org>,
	Jiri Olsa <jolsa@kernel.org>, Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Namhyung Kim <namhyung@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf scripts python: Let script to be python2 compliant
Date: Wed, 27 Jul 2022 18:17:03 +0200	[thread overview]
Message-ID: <YuFk/6rY4OXHlmjA@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <CABA31DoEJEyVeUgzROzzj_OA2exmj69WamaavQWi=7nWq52dxw@mail.gmail.com>

On Tue, Jul 26, 2022 at 01:35:40PM -0700, Akemi Yagi wrote:

> By the way, my main workstation runs RHEL 7. ;-)

That seems highly irresponsible, given the amount of security bugs fixed
by all the relevant projects.

  parent reply	other threads:[~2022-07-27 16:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-25 10:42 Leo Yan
2022-07-25 15:51 ` Arnaldo Carvalho de Melo
2022-07-26 16:56   ` Alan Bartlett
2022-07-26 17:52     ` Ian Rogers
2022-07-26 19:42       ` Arnaldo Carvalho de Melo
2022-07-26 20:35         ` Akemi Yagi
2022-07-26 20:54           ` Ian Rogers
2022-07-27 16:17           ` Peter Zijlstra [this message]
2022-07-26 20:43         ` Ian Rogers
2022-07-26 21:17           ` Arnaldo Carvalho de Melo
2022-08-17 19:52           ` Chuck Zmudzinski
2022-08-17 22:13             ` Chuck Zmudzinski
2022-08-17 22:36               ` Ian Rogers
2022-08-18  1:12                 ` Chuck Zmudzinski
2022-08-18  3:03                   ` Leo Yan
2022-08-18 14:52                     ` Ian Rogers
2022-08-19  6:48                       ` Leo Yan
2022-08-19 13:56                         ` Chuck Zmudzinski

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=YuFk/6rY4OXHlmjA@worktop.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=ajb@elrepo.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=contact@elrepo.org \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=leo.yan@linaro.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=toracat@elrepo.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

all inboxes | Powered by JetHome®