From: David Miller <davem@davemloft.net>
To: JBeulich@novell.com
Cc: dm@chelsio.com, divy@chelsio.com, linux-kbuild@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] cxgb{3,4}: streamline Kconfig options
Date: Mon, 28 Feb 2011 13:19:10 -0800 (PST) [thread overview]
Message-ID: <20110228.131910.242129416.davem@davemloft.net> (raw)
In-Reply-To: <4D6B68BE020000780003402E@vpn.id2.novell.com>
From: "Jan Beulich" <JBeulich@novell.com>
Date: Mon, 28 Feb 2011 08:19:58 +0000
>>>> On 25.02.11 at 20:51, Dimitris Michailidis <dm@chelsio.com> wrote:
>> Dimitris Michailidis wrote:
>>> Jan Beulich wrote:
>>>
>>>> As to that INET vs NET dependency - is it possible that the
>>>> network drivers really just need NET, but the iSCSI ones need
>>>> INET? In which case the only common dependency would be
>>>> PCI - certainly not worth a custom helper option.
>>>
>>> Reading the commit message that introduced CHELSIO_T3_DEPENDS, it talks
>>> of hidden dependencies that select does not see. I am not sure which
>>> exactly but since it's been a few years since that commit I'll try to
>>> see what the situation is today without the *_DEPENDS symbols and let
>>> you know.
>>
>> I looked into this and found that with the current Kconfig the iSCSI driver
>> does not appear in the SCSI menu until one first enables NETDEVICES and
>> NETDEV_10000 in the network driver menu. It appears that the *_DEPENDS
>> symbols were added to capture dependencies on such symbols within the
>> network driver Kconfig, besides the dependencies the driver's entry listed
>> explicitly.
>>
>> The patch below removes *T4*_DEPENDS and the network drivers' unnecessary
>> dependency on INET, and updates the iSCSI driver's entry so it is visible
>> without requiring any net driver options to be enabled first and has
>> adequate selects to be able to build the net driver (this part is adapted
>> from bnx2i's Kconfig entry). I still need to do the T3 part of this and
>> check that there isn't a conflict with the current scsi tree. Just for
>> review at this time.
>
> Thanks, this looks good to me.
Dimitris, please submit this anew with a proper commit log messag and
signoff. Thanks.
prev parent reply other threads:[~2011-02-28 21:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 13:29 [PATCH] cxgb{3,4}: streamline Kconfig options Jan Beulich
2011-02-22 18:14 ` David Miller
2011-02-23 9:46 ` Jan Beulich
2011-02-23 20:27 ` David Miller
2011-02-24 8:00 ` Jan Beulich
2011-02-24 19:41 ` Dimitris Michailidis
2011-02-25 19:51 ` Dimitris Michailidis
2011-02-28 8:19 ` Jan Beulich
2011-02-28 21:19 ` David Miller [this message]
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=20110228.131910.242129416.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=JBeulich@novell.com \
--cc=divy@chelsio.com \
--cc=dm@chelsio.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).