All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Schier <nicolas@fjasle.eu>
To: nicolas@fjasle.eu
Cc: stable@vger.kernel.org
Subject: [PATCH 4.14 0/2] Allow builds and script usage on current systems
Date: Wed, 26 May 2021 06:17:26 +0200	[thread overview]
Message-ID: <20210526041728.4114392-1-nicolas@fjasle.eu> (raw)

Current distributions start removing support for Python 2 (and thus
/usr/bin/python).  To still be able to build v4.14.y and to run
supplementary scripts fix shebang lines to use 'env' and switch
diffconfig and bloat-o-meter to Python 3 explicitly.

Python 3 availability should be given on v4.14 based distributions
(for comparison: Debian jessie 8 (est. 2013) shipped a 3.16 kernel and
Python 3).

Both upstream commits are originally included in v5.11 and re-applied on
v5.10, v5.4 and v4.19.


Andy Shevchenko (1):
  scripts: switch explicitly to Python 3

Finn Behrens (1):
  tweewide: Fix most Shebang lines

 Documentation/sphinx/parse-headers.pl                          | 2 +-
 Documentation/target/tcm_mod_builder.py                        | 2 +-
 Documentation/trace/postprocess/decode_msr.py                  | 2 +-
 Documentation/trace/postprocess/trace-pagealloc-postprocess.pl | 2 +-
 Documentation/trace/postprocess/trace-vmscan-postprocess.pl    | 2 +-
 arch/ia64/scripts/unwcheck.py                                  | 2 +-
 scripts/bloat-o-meter                                          | 2 +-
 scripts/config                                                 | 2 +-
 scripts/diffconfig                                             | 2 +-
 scripts/show_delta                                             | 2 +-
 scripts/sphinx-pre-install                                     | 2 +-
 scripts/tracing/draw_functrace.py                              | 2 +-
 tools/kvm/kvm_stat/kvm_stat                                    | 2 +-
 tools/perf/python/tracepoint.py                                | 2 +-
 tools/perf/python/twatch.py                                    | 2 +-
 tools/perf/scripts/python/call-graph-from-sql.py               | 2 +-
 tools/perf/scripts/python/sched-migration.py                   | 2 +-
 tools/perf/tests/attr.py                                       | 2 +-
 tools/perf/util/setup.py                                       | 2 +-
 tools/power/pm-graph/analyze_boot.py                           | 2 +-
 tools/power/pm-graph/analyze_suspend.py                        | 2 +-
 tools/power/x86/intel_pstate_tracer/intel_pstate_tracer.py     | 2 +-
 tools/testing/ktest/compare-ktest-sample.pl                    | 2 +-
 tools/testing/selftests/tc-testing/tdc_batch.py                | 2 +-
 24 files changed, 24 insertions(+), 24 deletions(-)

-- 
2.30.2


             reply	other threads:[~2021-05-26  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  4:17 Nicolas Schier [this message]
2021-05-26  4:17 ` [PATCH 4.14 1/2] tweewide: Fix most Shebang lines Nicolas Schier
2021-05-26  4:17 ` [PATCH 4.14 2/2] scripts: switch explicitly to Python 3 Nicolas Schier
2021-05-27  9:21 ` [PATCH 4.14 0/2] Allow builds and script usage on current systems Greg KH

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=20210526041728.4114392-1-nicolas@fjasle.eu \
    --to=nicolas@fjasle.eu \
    --cc=stable@vger.kernel.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.