From: Li kunyu <kunyu@nfschina.com>
To: rostedt@goodmis.org
Cc: agordeev@linux.ibm.com, aou@eecs.berkeley.edu,
borntraeger@linux.ibm.com, bp@alien8.de,
dave.hansen@linux.intel.com, gor@linux.ibm.com,
hca@linux.ibm.com, hpa@zytor.com, kunyu@nfschina.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-s390@vger.kernel.org, linux@armlinux.org.uk,
mingo@redhat.com, palmer@dabbelt.com, paul.walmsley@sifive.com,
svens@linux.ibm.com, tglx@linutronix.de, x86@kernel.org
Subject: Re: [PATCH] kernel: Ftrace seems to have functions to improve performance through optimization
Date: Thu, 12 May 2022 23:19:50 +0800 [thread overview]
Message-ID: <20220512151951.58197-1-kunyu@nfschina.com> (raw)
In-Reply-To: <20220512110725.22e69e3c@gandalf.local.home>
Thank you very much. Could I modify the description information of this patch and submit it again.
next prev parent reply other threads:[~2022-05-12 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 6:30 [PATCH] kernel: Ftrace seems to have functions to improve performance through optimization Li kunyu
2022-05-12 14:12 ` Steven Rostedt
2022-05-12 14:45 ` Li kunyu
2022-05-12 15:07 ` Steven Rostedt
2022-05-12 15:19 ` Li kunyu [this message]
2022-05-13 2:13 ` [PATCH] kernel: Ftrace seems to have functions to improve performance through optimization " Li kunyu
2022-05-17 14:13 ` Steven Rostedt
2022-05-18 2:36 ` [PATCH v2] ftrace: Remove return value of ftrace_arch_modify_*() Li kunyu
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=20220512151951.58197-1-kunyu@nfschina.com \
--to=kunyu@nfschina.com \
--cc=agordeev@linux.ibm.com \
--cc=aou@eecs.berkeley.edu \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=hpa@zytor.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mingo@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox