From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Mathieu Malaterre <malat@debian.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] perf/core: Move inline keyword at the beginning of declaration
Date: Tue, 26 Dec 2017 17:19:36 -0300 [thread overview]
Message-ID: <20171226201936.GX21971@kernel.org> (raw)
In-Reply-To: <CA+7wUsxWTkwR9hg4R0brY6nB2zYEj=Ka_r6TO+Z3FFdcizKCOw@mail.gmail.com>
Em Tue, Dec 26, 2017 at 07:23:08PM +0100, Mathieu Malaterre escreveu:
> Hi Arnaldo,
>
> On Tue, Dec 26, 2017 at 4:05 PM, Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
> > Em Tue, Dec 26, 2017 at 03:09:13PM +0100, Mathieu Malaterre escreveu:
> >> Fix non-fatal warning:
> >> kernel/events/core.c:6106:1: warning: ‘inline’ is not at beginning of declaration [-Wold-style-declaration]
> >> static void __always_inline
> >> ^~~~~~
> > Can you please provide more context? When did this become a problem?
> > What gcc version?
> I tend to use W=1 before submitting a patch since not everything is
> being caught by ./scripts/checkpatch.pl. So this trivial patch was
> simply a way for me to remove some warning pollution I was seeing on
> my branch (not clear why this specific warning is considered an error
> in other section of the linux tree). This is a custom pmac32 branch,
> gcc version is:
> $ powerpc-linux-gnu-gcc --version
> powerpc-linux-gnu-gcc (Debian 6.3.0-18) 6.3.0 20170516
> Feel free to drop it if this is too much noise.
Nah, I just like to have enough info on the cset as to where is that the
problem takes place, which you now have provided and I'll add to the
cset, thanks!
- Arnaldo
> Thanks
>
> > - Arnaldo
> >
> >> Signed-off-by: Mathieu Malaterre <malat@debian.org>
> >> ---
> >> kernel/events/core.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/kernel/events/core.c b/kernel/events/core.c
> >> index 4df5b695bf0d..aa874d2b58b3 100644
> >> --- a/kernel/events/core.c
> >> +++ b/kernel/events/core.c
> >> @@ -6103,7 +6103,7 @@ void perf_prepare_sample(struct perf_event_header *header,
> >> data->phys_addr = perf_virt_to_phys(data->addr);
> >> }
> >>
> >> -static void __always_inline
> >> +static __always_inline void
> >> __perf_event_output(struct perf_event *event,
> >> struct perf_sample_data *data,
> >> struct pt_regs *regs,
> >> --
> >> 2.11.0
next prev parent reply other threads:[~2017-12-26 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-26 14:09 Mathieu Malaterre
2017-12-26 15:05 ` Arnaldo Carvalho de Melo
2017-12-26 18:23 ` Mathieu Malaterre
2017-12-26 20:19 ` Arnaldo Carvalho de Melo [this message]
2018-06-26 20:23 ` [PATCH v2] " Mathieu Malaterre
2018-06-27 9:10 ` [tip:perf/urgent] " tip-bot for Mathieu Malaterre
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=20171226201936.GX21971@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=malat@debian.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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