From: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org, kbuild test robot <lkp@intel.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>,
kbuild-all@01.org
Subject: Re: [PATCH] ftrace: filter: Match dot symbols when searching functions on ppc64.
Date: Wed, 13 Apr 2016 21:39 -0300 [thread overview]
Message-ID: <2596502.8PPJLykyZv@hactar> (raw)
In-Reply-To: <3507082.VaWR3lh7Ni@hactar>
Hello,
Am Freitag, 01 April 2016, 18:28:06 schrieb Thiago Jung Bauermann:
> Am Samstag, 02 April 2016, 03:51:21 schrieb kbuild test robot:
> > >> arch/powerpc/include/asm/ftrace.h:62:5: error: "CONFIG_PPC64" is=
not
> > >> defined [-Werror=3Dundef]
> > >>=20
> > #if CONFIG_PPC64 && (!defined(_CALL_ELF) || _CALL_ELF !=3D 2)
> > =20
> > ^
> > =20
> > cc1: all warnings being treated as errors
>=20
> I forgot to use defined() in the #if expression. Here=E2=80=99s the f=
ixed version.
People seem to be considering patches for next, so this looks like a go=
od=20
moment to ping about this one.
Ps: patchwork seems to have an issue which causes it to show the messag=
e=20
body as if it were the commit message, but if you feed my original emai=
l=20
(the one I=E2=80=99m replying to here) to git am, the commit message wi=
ll be=20
correct.
--=20
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2016-04-14 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 3:22 [PATCH] ftrace: filter: Match dot symbols when searching functions on ppc64 Thiago Jung Bauermann
2016-04-01 19:51 ` kbuild test robot
2016-04-01 21:28 ` Thiago Jung Bauermann
2016-04-14 0:39 ` Thiago Jung Bauermann [this message]
2016-04-14 3:51 ` Steven Rostedt
2016-04-14 7:11 ` Michael Ellerman
2016-04-14 10:58 ` Steven Rostedt
2016-04-14 23:48 ` Thiago Jung Bauermann
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=2596502.8PPJLykyZv@hactar \
--to=bauerman@linux.vnet.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lkp@intel.com \
--cc=mingo@redhat.com \
--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).