mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Roland McGrath <roland@redhat.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: [PATCH] reorganize <linux/linkage.h>
Date: Fri, 11 Apr 2008 07:58:56 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.00.0804110747370.3143@woody.linux-foundation.org> (raw)
In-Reply-To: <20080411050019.GC27073@phobos.i.cabal.ca>


On Fri, 11 Apr 2008, Kyle McMartin wrote:
>
> Commit 54a015104136974262afa4b8ddd943ea70dec8a2 adds some new magic
> asmlinkage_protect gizmo, but that can only be used from C code, not
> assembly. Protect relevant bits of <linux/linkage.h> with !__ASSEMBLY__
> so this can't leak into assembly source.

Ok, so s390 had a similar issue, and I assumed that they were just usign a 
broken C pre-processor for asm, but now I'm starting to wonder about it.

Why cannot your pre-processor handle that thing?

It doesn't matter if it is C or assembly, the pre-processor should be the 
same. That #define isn't used for asm, so it shouldn't _matter_ for asm. 
What's going on?

I'm starting to suspect that it's the fact that some architectures still 
have

	EXTRA_AFLAGS  := -traditional

or equivalent and I'm wondering whether that is really necessary. IIRC x86 
got rid of the use of --traditional a long time ago, exactly because it 
caused problems with any fancier C preprocessor things.

It would probably be much better to try to lose that -traditional from 
affected architectures, because otherwise issues like this will keep 
popping up just because the most common architecture doesn't use the 
limited preprocessor..

		Linus

  reply	other threads:[~2008-04-11 15:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11  5:00 Kyle McMartin
2008-04-11 14:58 ` Linus Torvalds [this message]
2008-04-11 18:26   ` David Miller

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=alpine.LFD.1.00.0804110747370.3143@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kyle@mcmartin.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=schwidefsky@de.ibm.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

all inboxes | Powered by JetHome®