From: Greg KH <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>,
Tony Jones <tonyj@suse.de>, Jonathan Corbet <corbet@lwn.net>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@kernel.org>,
FRANJOU Stephane <stephane.franjou@csgroup.eu>,
linuxppc-dev@lists.ozlabs.org,
Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
Subject: Re: [PATCH] [Backport for 4.14] perf script python: Remove explicit shebang from tests/attr.c
Date: Mon, 19 Dec 2022 13:18:00 +0100 [thread overview]
Message-ID: <Y6BWeFdJiz/tIhQ6@kroah.com> (raw)
In-Reply-To: <3ca0515edb717e0f394f973f3cbbe2c80abb35e4.1671190496.git.christophe.leroy@csgroup.eu>
On Fri, Dec 16, 2022 at 12:38:12PM +0100, Christophe Leroy wrote:
> From: Tony Jones <tonyj@suse.de>
>
> [Upstream commit d72eadbc1d2866fc047edd4535ffb0298fe240be]
>
> tests/attr.c invokes attr.py via an explicit invocation of Python
> ($PYTHON) so there is therefore no need for an explicit shebang.
>
> Also most distros follow pep-0394 which recommends that /usr/bin/python
> refer only to v2 and so may not exist on the system (if PYTHON=python3).
>
> Signed-off-by: Tony Jones <tonyj@suse.de>
> Acked-by: Jiri Olsa <jolsa@kernel.org>
> Cc: Jonathan Corbet <corbet@lwn.net>
> Cc: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
> Cc: Seeteena Thoufeek <s1seetee@linux.vnet.ibm.com>
> Link: http://lkml.kernel.org/r/20190124005229.16146-5-tonyj@suse.de
> Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
> Signed-off-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
> tools/perf/tests/attr.py | 1 -
> 1 file changed, 1 deletion(-)
Why only 4.14? What about 4.19?
thanks,
greg k-h
next prev parent reply other threads:[~2022-12-19 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 11:38 [PATCH] [Backport for 4.14] perf script python: Remove explicit shebang from tests/attr.c Christophe Leroy
2022-12-19 12:18 ` Greg KH [this message]
2022-12-19 12:21 ` Christophe Leroy
2022-12-19 12:42 ` 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=Y6BWeFdJiz/tIhQ6@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=acme@redhat.com \
--cc=christophe.leroy@csgroup.eu \
--cc=corbet@lwn.net \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ravi.bangoria@linux.ibm.com \
--cc=s1seetee@linux.vnet.ibm.com \
--cc=stable@vger.kernel.org \
--cc=stephane.franjou@csgroup.eu \
--cc=tonyj@suse.de \
/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