lists.openwall.net   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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sun, 16 Mar 2014 11:27:04 +0800
From:	Chen Gang <gang.chen.5i5j@...il.com>
To:	Randy Dunlap <rdunlap@...radead.org>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Suggestion] Makefile: about allmodconfig issue.

On 03/16/2014 05:36 AM, Randy Dunlap wrote:
> On 03/15/2014 02:30 PM, Chen Gang wrote:
>> 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.
> 
> 
> If you can demonstrate a problem, then please submit a patch for it,
> but don't just hypothesize a problem, actually show that there is one.
>

We are discussing this gpio driver's issue, and also discussing one fix
patch (remove IRQ_DOMAIN dependency).

For me, when discussing one patch (e.g. this fix patch), it is necessary
for patch maker to provide proofs to clear all related doubts from any
members (e.g. me).

And theoretically, 'kbuild' need support (implement correctly) the
priority between 'select' and 'depends on', or it can not express all
related features (although it can not cause real world issue, now).


Thanks.
-- 
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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ