From: Jason Baron <jbaron@akamai.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Steven Rostedt <rostedt@goodmis.org>
Cc: peterz@infradead.org, mingo@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] jump_label: Fix anonymous union initialization
Date: Thu, 2 Mar 2017 16:07:19 -0500 [thread overview]
Message-ID: <1eba35cd-2b1f-64e5-0fe1-9756316b37b7@akamai.com> (raw)
In-Reply-To: <1488299542-30765-1-git-send-email-boris.ostrovsky@oracle.com>
On 02/28/2017 11:32 AM, Boris Ostrovsky wrote:
> Pre-4.6 gcc do not allow direct static initialization of members of
> anonymous structs/unions. After commit 3821fd35b58d ("jump_label:
> Reduce the size of struct static_key") STATIC_KEY_INIT_{TRUE|FALSE}
> definitions cannot be compiled with those older compilers.
>
> Placing initializers inside curved brackets works around this problem.
>
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> ---
> include/linux/jump_label.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/include/linux/jump_label.h b/include/linux/jump_label.h
> index 8e06d75..518020b 100644
> --- a/include/linux/jump_label.h
> +++ b/include/linux/jump_label.h
> @@ -166,10 +166,10 @@ extern void arch_jump_label_transform_static(struct jump_entry *entry,
> */
> #define STATIC_KEY_INIT_TRUE \
> { .enabled = { 1 }, \
> - .entries = (void *)JUMP_TYPE_TRUE }
> + { .entries = (void *)JUMP_TYPE_TRUE } }
> #define STATIC_KEY_INIT_FALSE \
> { .enabled = { 0 }, \
> - .entries = (void *)JUMP_TYPE_FALSE }
> + { .entries = (void *)JUMP_TYPE_FALSE } }
>
> #else /* !HAVE_JUMP_LABEL */
>
>
(Adding Steve to 'cc)
Thanks for the fix.
Reviewed-by: Jason Baron <jbaron@akamai.com>
Thanks,
-Jason
next prev parent reply other threads:[~2017-03-02 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 16:32 Boris Ostrovsky
2017-03-02 21:07 ` Jason Baron [this message]
2017-03-02 21:42 ` Steven Rostedt
2017-03-02 21:49 ` Chris Mason
2017-03-02 21:56 ` Boris Ostrovsky
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=1eba35cd-2b1f-64e5-0fe1-9756316b37b7@akamai.com \
--to=jbaron@akamai.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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
all inboxes | Powered by JetHome®