All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	Francois Bedard <Francois.Bedard@synopsys.com>,
	David Howells <dhowells@redhat.com>,
	Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] Revert "ARC: Add guard macro to uapi/asm/unistd.h"
Date: Thu, 19 Dec 2013 21:42:58 +0800	[thread overview]
Message-ID: <52B2F7E2.6020403@gmail.com> (raw)
In-Reply-To: <C2D7FE5348E1B147BCA15975FBA23075172B5E@IN01WEMBXA.internal.synopsys.com>

On 12/19/2013 09:11 PM, Vineet Gupta wrote:
> On 12/19/2013 06:04 PM, Chen Gang wrote:
>> On 12/19/2013 07:13 PM, Vineet Gupta wrote:
>>>> This reverts commit 97bc386fc12deeb41d5bff33548e3002b258d4e0.
>>>>
>>>> Generic syscall table generator relies on ARCH unistd.h as follows:
>>>>
>>>> 	void *sys_call_table[NR_syscalls] = {
>>>> 		[0 ... NR_syscalls-1] = sys_ni_syscall,
>>>> 	#include <asm/unistd.h>
>>>> 	};
>>>>
>>>> And turns out that prior dependencies already include that header by
>>>> the time preprocessor hits the above. Meaning ARCH unistd.h needs to be
>>>> able to included twice.
>>>>
>> OK, thanks, it sounds reasonable to me.
>>
>> But why many other architectures contents these guard macros? (arm, sh,
>> blackfin, cris, frv, ia64, m32r, m68k, mips, s390, microblaze, mn10300,
>> parisc, powerpc, sparc, x86). Do they need improvement too?
>>
>> And for our case, what xtensa has done looks like a better way to me.
> 
> Yeah, looks like that'll work - good find. Linus, please ignore the Revert, I'll
> follow up with a pull request.
> 

Thanks.  :-)

> -Vineet
> 


-- 
Chen Gang

Open, share and attitude like air, water and life which God blessed

      reply	other threads:[~2013-12-19 13:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19 11:13 [PATCH] Revert "ARC: Add guard macro to uapi/asm/unistd.h" Vineet Gupta
2013-12-19 12:34 ` Chen Gang
2013-12-19 12:42   ` Geert Uytterhoeven
2013-12-19 13:41     ` Chen Gang
2013-12-19 13:11   ` Vineet Gupta
2013-12-19 13:42     ` Chen Gang [this message]

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=52B2F7E2.6020403@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=Francois.Bedard@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.