From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] Makefile: about allmodconfig issue.
Date: Sun, 16 Mar 2014 05:30:47 +0800 [thread overview]
Message-ID: <5324C687.9070104@gmail.com> (raw)
In-Reply-To: <531E622A.5010200@gmail.com>
On 03/11/2014 09:08 AM, Chen Gang wrote:
> On 03/10/2014 12:24 AM, Randy Dunlap wrote:
>> On 03/09/2014 08:02 AM, Chen Gang wrote:
[...]
>>> Else ('depends on' priority is higher than 'select')
>>>
>>> - some architectures can choose whether support IRQ_DOMAIN.
>>>
>>> - if IRQ_DOMAIN enabled, our gpio driver can be used, and then select
>>> GENERIC_IRQ_CHIP (need not consider about it selects IRQ_DOMAIN).
>>>
>>> - else (IRQ_DOMAIN_disabled), we can not use our gpio driver, and also
>>> can not select GENERIC_IRQ_CHIP (need not consider about it selects
>>> IRQ_DOMAIN, either).
>>>
>>> Excuse me, I am not quite familiar with Kconfig grammar, can any members
>>> give a confirmation for it (whether 'select' priority is higher or equal
>>> than 'depends on').
>>
>> Sorry, I don't really understand the problem that you are trying to solve.
>> Maybe you could back up and explain the underlying problem... ?
>>
>
> If the fix patch applied (don't depend on IRQ_DOMAIN), I guess, if one
> architecture don't support IRQ_DOMAIN, GPIO_DWAPB may still be enabled
> and then let IRQ_DOMAIN enable too.
>
Is it possible to still go further? For me, I still think, this is not
gpio driver's issue, the kbuild need be improved to support this using case.
So, if it is necessary, I will/should try to go further about it.
Thanks.
--
Chen Gang
Open, share and attitude like air, water and life which God blessed
next prev parent reply other threads:[~2014-03-15 21:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-08 13:07 [Suggestion] Makefile: about allmodconfig issue Chen Gang
2014-03-08 15:04 ` Randy Dunlap
2014-03-08 21:44 ` Chen Gang
2014-03-08 21:58 ` Randy Dunlap
2014-03-09 15:02 ` Chen Gang
2014-03-09 16:24 ` Randy Dunlap
2014-03-11 1:08 ` Chen Gang
2014-03-15 21:30 ` Chen Gang [this message]
2014-03-15 21:36 ` Randy Dunlap
2014-03-16 3:27 ` 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=5324C687.9070104@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox