public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Fernando Fernandez Mancera <fmancera@suse.de>
To: Alyssa Ross <hi@alyssa.is>,
	"David S. Miller" <davem@davemloft.net>,
	David Ahern <dsahern@kernel.org>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Simon Horman <horms@kernel.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Ricardo B . Marlière" <rbm@suse.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>
Subject: Re: [PATCH v2] ipv6: default IPV6_SIT to m
Date: Tue, 5 May 2026 22:17:23 +0200	[thread overview]
Message-ID: <8064df33-daa4-430d-ac0c-3cbf2911f98a@suse.de> (raw)
In-Reply-To: <20260503192515.290900-2-hi@alyssa.is>

On 5/3/26 9:25 PM, Alyssa Ross wrote:
> This basically defaulted to m until recently, since IPV6 defaulted to
> m.  Since IPV6 was changed to a boolean with a default of y, IPV6_SIT
> started defaulting to built-in as well.  This results in a surprise
> sit0 device by default for defconfig (and defconfig-derived config)
> users at boot.  For me, this broke an (admittedly non-robust) script.
> Preserve the behaviour of most configs by avoiding building this
> module, that's probably overall seldom used compared to IPv6 as a
> whole, into the kernel.
> 
> Fixes: 309b905deee59 ("ipv6: convert CONFIG_IPV6 to built-in only and clean up Kconfigs")
> Signed-off-by: Alyssa Ross <hi@alyssa.is>

As discussed:

Reviewed-by: Fernando Fernandez Mancera <fmancera@suse.de>

Thanks!

  parent reply	other threads:[~2026-05-05 20:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-03 19:25 [PATCH v2] ipv6: default IPV6_SIT to m Alyssa Ross
2026-05-04 10:30 ` Fernando Fernandez Mancera
2026-05-04 14:30   ` Alyssa Ross
2026-05-04 15:01     ` Fernando Fernandez Mancera
2026-05-05  0:09       ` Jakub Kicinski
2026-05-05 20:16         ` Fernando Fernandez Mancera
2026-05-05 20:17 ` Fernando Fernandez Mancera [this message]
2026-05-06  0:40 ` patchwork-bot+netdevbpf

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=8064df33-daa4-430d-ac0c-3cbf2911f98a@suse.de \
    --to=fmancera@suse.de \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=hi@alyssa.is \
    --cc=horms@kernel.org \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rbm@suse.com \
    /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