From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: linuxppc-dev@lists.ozlabs.org, Stuart Yoder <stuart.yoder@freescale.com>
Subject: Re: [PATCH] PPC: use CURRENT_THREAD_INFO instead of open coded assembly
Date: Tue, 03 Jul 2012 07:26:08 +1000 [thread overview]
Message-ID: <1341264368.2588.49.camel@pasglop> (raw)
In-Reply-To: <40388C8A-6D3B-409E-9C6D-45005E1F6016@suse.de>
On Mon, 2012-07-02 at 22:59 +0200, Alexander Graf wrote:
> This should go into an #ifdef __ASSEMBLY__ block, right? :)
We almost never use #ifdef __ASSEMBLY__, we use it the other way around,
to prevent C stuff from being included in assembly. The other way around
is legit since things might be used in inline asm for example.
Cheers,
Ben.
next prev parent reply other threads:[~2012-07-02 21:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 20:56 [PATCH] PPC: use CURRENT_THREAD_INFO instead of open coded assembly Stuart Yoder
2012-07-02 20:59 ` Alexander Graf
2012-07-02 21:26 ` Benjamin Herrenschmidt [this message]
2012-07-02 21:27 ` Alexander Graf
2012-07-02 21:31 ` Scott Wood
2012-07-02 21:34 ` Alexander Graf
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=1341264368.2588.49.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=stuart.yoder@freescale.com \
/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).