From: "H. Peter Anvin" <hpa@zytor.com>
To: Jiri Slaby <jslaby@suse.cz>, rostedt@goodmis.org
Cc: jirislaby@gmail.com, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
x86@kernel.org, Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 2/2] fentry: x86, cleanup function_hook uses
Date: Tue, 29 Apr 2014 00:28:16 -0700 [thread overview]
Message-ID: <535F5490.5020504@zytor.com> (raw)
In-Reply-To: <1398756247-29536-2-git-send-email-jslaby@suse.cz>
On 04/29/2014 12:24 AM, Jiri Slaby wrote:
> Let's define fentry_hook depending on CC_USING_FENTRY and use that
> macro all over. This saves some #ifdef's here and there.
Any reason not to use the existing macro name function_hook?
(Valid reasons include "too generic". However, please motivate in the
commit message.)
-hpa
next prev parent reply other threads:[~2014-04-29 7:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 7:24 [PATCH 1/2] ftrace: PPC, fix obsolete comment Jiri Slaby
2014-04-29 7:24 ` [PATCH 2/2] fentry: x86, cleanup function_hook uses Jiri Slaby
2014-04-29 7:28 ` H. Peter Anvin [this message]
2014-04-29 10:47 ` [PATCH v2 " Jiri Slaby
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=535F5490.5020504@zytor.com \
--to=hpa@zytor.com \
--cc=fweisbec@gmail.com \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--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
Powered by JetHome