From: Torsten Duwe <duwe@lst.de>
To: Steven Rostedt <rostedt@goodmis.org>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Jiri Kosina <jkosina@suse.cz>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] ppc64 LE ABI v2 ftrace-with-regs implementation
Date: Fri, 19 Jun 2015 16:04:03 +0200 [thread overview]
Message-ID: <20150619140403.GA8681@lst.de> (raw)
Changes since v1: adjusted dashes, whitespace, make checkpatch happy.
No functional changes.
Do NOT select FTRACE_WITH_REGS on ELF ABI v1 !
For C source, there's
#if defined(_CALL_ELF) && _CALL_ELF == 2
Maybe there's something for Kconfig, too.
Torsten
next reply other threads:[~2015-06-19 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 14:04 Torsten Duwe [this message]
2015-06-19 14:07 ` [PATCH v2 1/4] ppc64 FTRACE_WITH_REGS implementation Torsten Duwe
2015-06-19 14:08 ` [PATCH v2 2/4] ppc64 ftrace_with_regs configuration variables Torsten Duwe
2015-06-19 14:09 ` [PATCH v2 3/4] ppc64 ftrace_with_regs: spare early boot and low level code Torsten Duwe
2015-06-19 14:09 ` [PATCH v2 4/4] ppc64 ftrace_with_regs recursion protection Torsten Duwe
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=20150619140403.GA8681@lst.de \
--to=duwe@lst.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).