From: Chen Gang <gang.chen.5i5j@gmail.com>
To: David Rientjes <rientjes@google.com>
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] arch/score/include/uapi/asm/ptrace.h: Add prefix 'SCORE_' for related macros
Date: Mon, 23 Jun 2014 18:31:49 +0800 [thread overview]
Message-ID: <53A80215.5090200@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1406230237330.8821@chino.kir.corp.google.com>
On 06/23/2014 05:38 PM, David Rientjes wrote:
> On Sun, 22 Jun 2014, Chen Gang wrote:
>
>> diff --git a/arch/score/include/uapi/asm/ptrace.h b/arch/score/include/uapi/asm/ptrace.h
>> index f59771a..7a0ead9 100644
>> --- a/arch/score/include/uapi/asm/ptrace.h
>> +++ b/arch/score/include/uapi/asm/ptrace.h
>> @@ -4,16 +4,16 @@
>> #define PTRACE_GETREGS 12
>> #define PTRACE_SETREGS 13
>>
>> -#define PC 32
>> -#define CONDITION 33
>> -#define ECR 34
>> -#define EMA 35
>> -#define CEH 36
>> -#define CEL 37
>> -#define COUNTER 38
>> -#define LDCR 39
>> -#define STCR 40
>> -#define PSR 41
>> +#define SCORE_PC 32
>> +#define SCORE_CONDITION 33
>> +#define SCORE_ECR 34
>> +#define SCORE_EMA 35
>> +#define SCORE_CEH 36
>> +#define SOCRE_CEL 37
>
> SOCRE?
>
OH, typo issue, thanks.
>> +#define SCORE_COUNTER 38
>> +#define SCORE_LDCR 39
>> +#define SCORE_STCR 40
>> +#define SCORE_PSR 41
>>
>> #define SINGLESTEP16_INSN 0x7006
>> #define SINGLESTEP32_INSN 0x840C8000
>
> This is a uapi header file, what was done to ensure this doesn't introduce
> userspace breakage?
>
Do you have any new idea for it, since you have question?
For me, one solving way is: use "#if defined(__KERNEL__) &&
defined(__LINUX__)" for check whether need a prefix (e.g. 'SCORE_') for it.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
prev parent reply other threads:[~2014-06-23 10:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-22 4:48 [PATCH] arch/score/include/uapi/asm/ptrace.h: Add prefix 'SCORE_' for related macros Chen Gang
2014-06-22 5:16 ` Guenter Roeck
2014-06-22 5:33 ` Chen Gang
2014-06-22 14:53 ` Guenter Roeck
2014-06-22 15:02 ` Guenter Roeck
2014-06-23 3:03 ` Chen Gang
2014-06-24 13:24 ` Chen Gang
2014-06-24 14:44 ` Guenter Roeck
2014-06-25 0:28 ` Chen Gang
2014-06-27 10:12 ` Chen Gang
2014-06-30 1:42 ` Chen Gang
2014-06-22 8:09 ` Lennox Wu
2014-06-22 16:28 ` Guenter Roeck
2014-06-23 3:07 ` Chen Gang
2014-06-23 3:13 ` Lennox Wu
2014-06-23 3:10 ` Lennox Wu
2014-06-23 4:44 ` Chen Gang
2014-06-23 9:38 ` David Rientjes
2014-06-23 10:31 ` 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=53A80215.5090200@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=lennox.wu@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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).