linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Vincent Pelletier <plr.vincent@gmail.com>,
	Andy Whitcroft <apw@canonical.com>,
	Dwaipayan Ray <dwaipayanray1@gmail.com>,
	Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
	Yonghong Song <yhs@fb.com>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org
Subject: Re: [PATCH] checkpatch: Follow scripts/spdxcheck.py's switch to python3
Date: Thu, 08 Jul 2021 10:25:32 -0700	[thread overview]
Message-ID: <5f054b8ea1057f1485f8af3546b45bdfd0c21acb.camel@perches.com> (raw)
In-Reply-To: <73dca402670be1e7a8adf139621dafd0dfa03191.1625740121.git.plr.vincent@gmail.com>

On Thu, 2021-07-08 at 10:29 +0000, Vincent Pelletier wrote:
> Since commit d0259c42abff ("spdxcheck.py: Use Python 3") spdxcheck.py
> expects to be run using python3. "python" may still be a python2 alias.
> Instead, obey scripts/spdxcheck.py's shebang by executing it without
> pre-selecting an interpreter.
> Also, test python3 presence in path.

Thanks, but already done. See:

commit f9363b31d769245cb7ec8a660460800d4b466911
Author: Guenter Roeck <linux@roeck-us.net>
Date:   Wed Jun 30 18:56:19 2021 -0700

    checkpatch: scripts/spdxcheck.py now requires python3



      reply	other threads:[~2021-07-08 17:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08 10:29 [PATCH] checkpatch: Follow scripts/spdxcheck.py's switch to python3 Vincent Pelletier
2021-07-08 17:25 ` Joe Perches [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=5f054b8ea1057f1485f8af3546b45bdfd0c21acb.camel@perches.com \
    --to=joe@perches.com \
    --cc=andrii@kernel.org \
    --cc=apw@canonical.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=dwaipayanray1@gmail.com \
    --cc=john.fastabend@gmail.com \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=plr.vincent@gmail.com \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.com \
    /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).