From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>, Lennox Wu <lennox.wu@gmail.com>
Cc: Liqin Chen <liqin.linux@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 11:07:17 +0800 [thread overview]
Message-ID: <53A799E5.7040609@gmail.com> (raw)
In-Reply-To: <53A70420.4010005@roeck-us.net>
On 06/23/2014 12:28 AM, Guenter Roeck wrote:
> On 06/22/2014 01:09 AM, Lennox Wu wrote:
>> Hi Chen,
>> Do you find other modules except device modules cause issues of
>> compiling?
>> The applications of Score are limited. Acutally, some errors never occur
>> in the limited applications, for example, the conbination consists of
>> Score and the timer of SuperH. I'm not sure we should handle this kind
>> of error.
>> If the rule is that we should make sure "all" modules can be compiled
>> with Score, we will do it.
>> However, we still thanks for your check.
>>
>
> Other architectures don't care about buildability of allmodconfig or
> allyesconfig
> (arm is a good [or maybe bad] example), so it is for sure not mandatory.
> On the other side, fixing such problems - especially when you have someone
> doing it for you - may prevent problems down the road, so while not
> mandatory
> I consider it a useful goal to achieve.
>
> If there is a driver which doesn't make sense to build at all, such as
> the SuperH
> timer driver mentioned above, it can always be excluded from building
> with Kconfig.
> If that causes opposition for some reason, you can still ignore that it
> fails
> to build.
>
Yeah, what Guenter said is fine to me.
Although allmodconfig is not mandatory, it is still a useful goal to
achieve.
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-06-23 3:07 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 [this message]
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
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=53A799E5.7040609@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 \
/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).