From: Chen Gang <gang.chen.5i5j@gmail.com>
To: David Rientjes <rientjes@google.com>, Guenter Roeck <linux@roeck-us.net>
Cc: Liqin Chen <liqin.linux@gmail.com>,
Lennox Wu <lennox.wu@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] rch/score/include/uapi/asm/ptrace.h: Add prefix 'SCORE_' for related macros
Date: Wed, 25 Jun 2014 09:25:49 +0800 [thread overview]
Message-ID: <53AA251D.9070100@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406241639310.22030@chino.kir.corp.google.com>
On 06/25/2014 07:40 AM, David Rientjes wrote:
> On Tue, 24 Jun 2014, Guenter Roeck wrote:
>
>> That is another question. But for the time being it might be sufficient to
>> surround the defines with #if !defined(__KERNEL__) without introducing new
>> (and unused) kernel defines.
>>
>
> On the other hand, if no userspace is referencing these, then you could
> just rename them and move them out of the uapi header to
> include/asm/ptrace.h and be done with it.
>
OK, thanks. And sorry for the subject lost 'a', firstly. And it is
related with UAPI, so it is really important enough to let related
maintainer to notice about it.
I guess, only the related maintainer know whether can remove these
macros out of "include/uapi/asm/ptrace.h" (although in current upstream
kernel source, they are really not used).
It is abnormal in uapi headers for same values with different macros
switched by "__KERNEL__", but if we have to remain them still in uapi,
we have to use "__KERNEL__ && __linux__" to carm down kernel and user.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-06-25 1:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 13:08 [PATCH v2] rch/score/include/uapi/asm/ptrace.h: Add prefix 'SCORE_' for related macros Chen Gang
2014-06-24 14:47 ` Guenter Roeck
2014-06-24 22:51 ` David Rientjes
2014-06-24 23:10 ` Guenter Roeck
2014-06-24 23:40 ` David Rientjes
2014-06-25 1:25 ` Chen Gang [this message]
2014-06-25 15:16 ` Lennox Wu
2014-06-25 22:09 ` Chen Gang
[not found] <BAY404-EAS3244E3E66FF1100E4753CC9B0180@phx.gbl>
2014-06-26 0:30 ` Guenter Roeck
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=53AA251D.9070100@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liqin.linux@gmail.com \
--cc=rientjes@google.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 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.