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 12:05:49 -0300 [thread overview]
Message-ID: <20171226150549.GW21971@kernel.org> (raw)
In-Reply-To: <20171226140913.16640-1-malat@debian.org>
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?
- 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 15:05 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 [this message]
2017-12-26 18:23 ` Mathieu Malaterre
2017-12-26 20:19 ` Arnaldo Carvalho de Melo
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=20171226150549.GW21971@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