[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200817.143438.857390576001965310.davem@davemloft.net>
Date: Mon, 17 Aug 2020 14:34:38 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: xiyou.wangcong@...il.com
Cc: rdunlap@...radead.org, lucien.xin@...il.com,
netdev@...r.kernel.org, jmaloy@...hat.com, ying.xue@...driver.com,
tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net] tipc: not enable tipc when ipv6 works as a module
From: Cong Wang <xiyou.wangcong@...il.com>
Date: Mon, 17 Aug 2020 11:55:55 -0700
> On Mon, Aug 17, 2020 at 11:49 AM Randy Dunlap <rdunlap@...radead.org> wrote:
>>
>> It just restricts how TIPC can be built, so that
>> TIPC=y and IPV6=m cannot happen together, which causes
>> a build error.
>
> It also disallows TIPC=m and IPV6=m, right?
That combination is allowed.
The whole "X || X=n" construct means X must be off or equal to the
value of the Kconfig entry this dependency is for.
Thus you'll see "depends IPV6 || IPV6=n" everywhere.
Powered by blists - more mailing lists