From: Randy Dunlap <rdunlap@infradead.org>
To: Chen Gang <gang.chen.5i5j@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] Makefile: about allmodconfig issue.
Date: Sun, 09 Mar 2014 09:24:30 -0700 [thread overview]
Message-ID: <531C95BE.1070306@infradead.org> (raw)
In-Reply-To: <531C8269.4010105@gmail.com>
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
next prev parent reply other threads:[~2014-03-09 16:24 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 [this message]
2014-03-11 1:08 ` Chen Gang
2014-03-15 21:30 ` Chen Gang
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=531C95BE.1070306@infradead.org \
--to=rdunlap@infradead.org \
--cc=gang.chen.5i5j@gmail.com \
--cc=linux-kernel@vger.kernel.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