From: Jason Baron <jbaron@akamai•com>
To: Anton Blanchard <anton@samba•org>,
"benh@kernel•crashing.org" <benh@kernel•crashing.org>,
"paulus@samba•org" <paulus@samba•org>,
"mpe@ellerman•id.au" <mpe@ellerman•id.au>,
"mmarek@suse•cz" <mmarek@suse•cz>,
"akpm@linux-foundation•org" <akpm@linux-foundation•org>,
"peterz@infradead•org" <peterz@infradead•org>,
"liuj97@gmail•com" <liuj97@gmail•com>,
"mingo@kernel•org" <mingo@kernel•org>,
"mgorman@suse•de" <mgorman@suse•de>,
rostedt@goodmis•org
Cc: "linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"linux-kbuild@vger•kernel.org" <linux-kbuild@vger•kernel.org>
Subject: Re: [PATCH 1/2] jump_label: Allow jump labels to be used in assembly
Date: Tue, 06 Jan 2015 10:46:54 -0500 [thread overview]
Message-ID: <54AC036E.6080507@akamai.com> (raw)
In-Reply-To: <1420539628-17875-1-git-send-email-anton@samba.org>
On 01/06/2015 05:20 AM, Anton Blanchard wrote:
> To use jump labels in assembly we need the HAVE_JUMP_LABEL define,
> so we select a fallback version if the toolchain does not support
> them.
>
> Modify linux/jump_label.h so it can be included by assembly files.
> We also need to add -DCC_HAVE_ASM_GOTO to KBUILD_AFLAGS.
>
> Signed-off-by: Anton Blanchard <anton@samba•org>
(adding Steven)
Acked-by: Jason Baron <jbaron@akamai•com>
The jump label stuff often gets picked up by Steve, but I guess this
could go through the powerpc tree as well...
Thanks,
-Jason
next prev parent reply other threads:[~2015-01-06 15:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 10:20 [PATCH 1/2] jump_label: Allow jump labels to be used in assembly Anton Blanchard
2015-01-06 10:20 ` [PATCH 2/2] powerpc: Include linux/jump_label.h to get HAVE_JUMP_LABEL define Anton Blanchard
2015-01-06 15:46 ` Jason Baron [this message]
2015-01-06 17:48 ` [PATCH 1/2] jump_label: Allow jump labels to be used in assembly Steven Rostedt
2015-01-07 10:34 ` Anton Blanchard
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=54AC036E.6080507@akamai.com \
--to=jbaron@akamai$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=anton@samba$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linux-kbuild@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=liuj97@gmail$(echo .)com \
--cc=mgorman@suse$(echo .)de \
--cc=mingo@kernel$(echo .)org \
--cc=mmarek@suse$(echo .)cz \
--cc=mpe@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
--cc=peterz@infradead$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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