From: Chuck Zmudzinski <brchuckz@netscape.net>
To: Leo Yan <leo.yan@linaro.org>, Ian Rogers <irogers@google.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
Alan Bartlett <ajb@elrepo.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
linux-perf-users@vger.kernel.org, ElRepo <contact@elrepo.org>,
Akemi Yagi <toracat@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: Fri, 19 Aug 2022 09:56:26 -0400 [thread overview]
Message-ID: <a0950172-aab0-a771-0255-d3654f217ce8@netscape.net> (raw)
In-Reply-To: <Yv8yRv2BMVgmb/n+@leoy-yangtze.lan>
On 8/19/2022 2:48 AM, Leo Yan wrote:
> On Thu, Aug 18, 2022 at 07:52:22AM -0700, Ian Rogers wrote:
>
> [...]
>
> > > > I see this has already been committed. I agree it should not
> > > > stay in the kernel tree for long. At some point in the future
> > > > it will most likely cause problems if it is not reverted.
> > >
>
>
> It's fine for me to revert this patch in an appropriate time.
An appropriate time presumably means when there is no more significant
demand for mainline kernel support on older distros like RHEL 7 and clones
that are still using python2. I also presume you plan to post the proposed
revert to the appropriate mailing lists before committing it, giving time for
anyone who wants to keep python2 compatibility a chance to make their
case.
Thanks,
Chuck
prev parent reply other threads:[~2022-08-19 13:56 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
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 [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=a0950172-aab0-a771-0255-d3654f217ce8@netscape.net \
--to=brchuckz@netscape.net \
--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=peterz@infradead.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®