Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Xin Long <lucien.xin@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>,
	Jon Maloy <jmaloy@redhat.com>, Ying Xue <ying.xue@windriver.com>
Cc: David Miller <davem@davemloft.net>,
	Randy Dunlap <rdunlap@infradead.org>,
	Linux Kernel Network Developers <netdev@vger.kernel.org>,
	tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH net] tipc: not enable tipc when ipv6 works as a module
Date: Tue, 18 Aug 2020 15:59:59 +0800	[thread overview]
Message-ID: <CADvbK_erTeDHk_Mh911=3AhSnL1+YNXNau-sLgm_2_eMUixvjQ@mail.gmail.com> (raw)
In-Reply-To: <CAM_iQpUZZeZ-RYr-+h=r2TV7evL5AuJXe5gcso14TtBE+U82fg@mail.gmail.com>

On Tue, Aug 18, 2020 at 6:20 AM Cong Wang <xiyou.wangcong@gmail.com> wrote:
>
> On Mon, Aug 17, 2020 at 2:39 PM David Miller <davem@davemloft.net> wrote:
> >
> > From: Cong Wang <xiyou.wangcong@gmail.com>
> > Date: Mon, 17 Aug 2020 13:59:46 -0700
> >
> > > Is this a new Kconfig feature? ipv6_stub was introduced for
> > > VXLAN, at that time I don't remember we have such kind of
> > > Kconfig rules, otherwise it would not be needed.
> >
> > The ipv6_stub exists in order to allow the troublesome
> > "ipv6=m && feature_using_ipv6=y" combination.
For certain code, instead of IS_ENABLE(), use IS_REACHABLE().

>
> Hmm, so "IPV6=m && TIPC=y" is not a concern here as you pick
> this patch over adding a ipv6_stub?
>
This is more a question for TIPC users.

Hi, Jon and Ying,

Have you met any users having "IPV6=m && TIPC=y" in their kernels?

  reply	other threads:[~2020-08-18  7:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-16  9:32 Xin Long
2020-08-16 18:29 ` Cong Wang
2020-08-17  6:49   ` Xin Long
2020-08-17 18:31     ` Cong Wang
2020-08-17 18:49       ` Randy Dunlap
2020-08-17 18:55         ` Cong Wang
2020-08-17 19:00           ` Randy Dunlap
2020-08-17 19:26             ` Cong Wang
2020-08-17 19:55               ` Randy Dunlap
2020-08-17 20:29                 ` Cong Wang
2020-08-17 20:43                   ` Randy Dunlap
2020-08-17 20:59                     ` Cong Wang
2020-08-17 21:39                       ` David Miller
2020-08-17 22:20                         ` Cong Wang
2020-08-18  7:59                           ` Xin Long [this message]
2020-08-17 21:37                   ` David Miller
2020-08-17 21:34           ` David Miller
2020-08-17  4:05 ` David Miller

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='CADvbK_erTeDHk_Mh911=3AhSnL1+YNXNau-sLgm_2_eMUixvjQ@mail.gmail.com' \
    --to=lucien.xin@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jmaloy@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=tipc-discussion@lists.sourceforge.net \
    --cc=xiyou.wangcong@gmail.com \
    --cc=ying.xue@windriver.com \
    --subject='Re: [PATCH net] tipc: not enable tipc when ipv6 works as a module' \
    /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

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