lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 11 Mar 2014 09:08:58 +0800
From:	Chen Gang <>
To:	Randy Dunlap <>
CC:	"" <>
Subject: Re: [Suggestion] Makefile: about allmodconfig issue.

On 03/10/2014 12:24 AM, Randy Dunlap wrote:
> 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:
>> 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"?

Only point to GPIO_DWAPB driver.

For me, if its full source code are in our upstream kernel, we need
treat it as "our source code". So when we find an issue about it, we can
also treat it as our issue.

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

OK, thanks, I will/should read it completely.

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

Chen Gang

Open, share, and attitude like air, water, and life which God blessed
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists