From: Andi Kleen <ak@linux.intel.com>
To: Rong Tao <rtoax@foxmail.com>
Cc: corbet@lwn.net, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, rongtao@cestc.cn
Subject: Re: [PATCH] docs: trace: Convert decode_msr.py print syntax to python3
Date: Sun, 25 Jun 2023 07:57:22 -0700 [thread overview]
Message-ID: <ZJhV0lQw59czLEGl@tassilo> (raw)
In-Reply-To: <tencent_69EBD5683EE28741BE906B56C8E59D8AE906@qq.com>
On Sun, Jun 25, 2023 at 09:03:57AM +0800, Rong Tao wrote:
> Thanks for your reply, jon. How about i submit v2 to remove decode_msr.py
> totally?
Well only if you can explain how the MSR tracer should be used without
it?
Not sure I understand the whole discussion here.
-Andi
prev parent reply other threads:[~2023-06-25 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 7:44 [PATCH] docs: trace: Convert decode_msr.py print syntax to python3 Rong Tao
2023-06-21 15:14 ` Jonathan Corbet
2023-06-25 1:03 ` Rong Tao
2023-06-25 14:57 ` Andi Kleen [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=ZJhV0lQw59czLEGl@tassilo \
--to=ak@linux.intel.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.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).