Re: [Suggestion] Makefile: about allmodconfig issue.

From: Randy Dunlap
Date: Sun Mar 09 2014 - 12:24:40 EST


On 03/09/2014 08:02 AM, Chen Gang wrote:
> On 03/09/2014 05:58 AM, Randy Dunlap wrote:
>> On 03/08/2014 01:44 PM, Chen Gang wrote:
>>> On 03/08/2014 11:04 PM, Randy Dunlap wrote:
>>>> On 03/08/2014 05:07 AM, Chen Gang wrote:
>>> [...]
>>>>> Welcome any suggestions, discussions and completions.
>>>>>
>>>>> Thanks.
>>>>>
>>>>
>>>> A patch has already been submitted and applied by the subsystem maintainer.
>>>>
>>>> http://marc.info/?l=linux-gpio&m=139413626320431&w=2
>>>>
>>>>
>>>
>>> OK, Thanks. And excuse me, I can not connect to this web site in China.
>>>
>>> Could you please past the patch contents in the reply mail? (or just let
>>> me know whether it is "make allmodconfig" issue, or only gpio driver's
>>> issue)
>>>
>>>
>>> Thanks.
>>
>> It's a gpio driver Kconfig patch -- not an allmodconfig issue.
>>
>
> Can we say that the 'select' priority is higher or equal than 'depends
> on'? If we really can say so, we need change our gpio driver.

what driver is "our gpio driver"?

Documentation/kbuild/kconfig-language.txt does not talk about priorities
of depends or select.

> 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... ?


--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/