From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: Jeremy Cline <jcline@redhat.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
Frederic Weisbecker <fweisbec@gmail.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] scripts: Add Python 3 support to tracing/draw_functrace.py
Date: Sun, 29 Jul 2018 11:11:21 +0900 [thread overview]
Message-ID: <CAK7LNASS_LfGOPthtL0Quueh74Sbatdhk0ouaRUZuufNB1VSvw@mail.gmail.com> (raw)
In-Reply-To: <20180728144833.6336-1-jcline@redhat.com>
2018-07-28 23:48 GMT+09:00 Jeremy Cline <jcline@redhat.com>:
> Use the print function. This maintains Python 2 support and should have
> no functional change.
>
> Signed-off-by: Jeremy Cline <jcline@redhat.com>
> ---
Applied to linux-kbuild. Thanks!
> Changes from v1:
> - Drop "from __future__ import print_function" as Python 2 is not long
> for this world and in this case the statement and function behave
> the same way.
>
> scripts/tracing/draw_functrace.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/scripts/tracing/draw_functrace.py b/scripts/tracing/draw_functrace.py
> index db40fa04cd51..9b6dd4f36335 100755
> --- a/scripts/tracing/draw_functrace.py
> +++ b/scripts/tracing/draw_functrace.py
> @@ -123,7 +123,7 @@ def main():
> tree = tree.getParent(caller)
> tree = tree.calls(callee, calltime)
>
> - print CallTree.ROOT
> + print(CallTree.ROOT)
>
> if __name__ == "__main__":
> main()
> --
> 2.17.1
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Best Regards
Masahiro Yamada
prev parent reply other threads:[~2018-07-29 2:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 14:48 Jeremy Cline
2018-07-29 2:11 ` Masahiro Yamada [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=CAK7LNASS_LfGOPthtL0Quueh74Sbatdhk0ouaRUZuufNB1VSvw@mail.gmail.com \
--to=yamada.masahiro@socionext.com \
--cc=fweisbec@gmail.com \
--cc=jcline@redhat.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
/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®