All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Fernando Fernandez Mancera <fmancera@suse.de>
Cc: "Alyssa Ross" <hi@alyssa.is>,
	"David S. Miller" <davem@davemloft.net>,
	"David Ahern" <dsahern@kernel.org>,
	"Eric Dumazet" <edumazet@google.com>,
	"Paolo Abeni" <pabeni@redhat.com>,
	"Simon Horman" <horms@kernel.org>,
	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: Mon, 4 May 2026 17:09:12 -0700	[thread overview]
Message-ID: <20260504170912.174235db@kernel.org> (raw)
In-Reply-To: <d299649e-d01e-451a-b604-76c8662f1ecc@suse.de>

On Mon, 4 May 2026 17:01:43 +0200 Fernando Fernandez Mancera wrote:
> > Yes, it appears you're right.  I had only tested on ARM.  In that case,
> > perhaps it make sense to instead set this to m in the arm64 defconfig, to
> > preserve the previous situation, but I can also see the value in
> > reducing platform discongruity by letting it change to y on arm64 too.  
> 
> Changing it on arm64 defconfig would make sense to me too. We should 
> probably visit other configs that might be in the same situation. That 
> in my opinion would qualify a net tree fix as you proposed initially.

Right. I think the fix as posted makes sense. Tunnel drivers should 
be =m. If other arches default to =y that's likely an oversight.
Fedora and I suspect all other distros (and "prod kernels") set SIT=m.

  reply	other threads:[~2026-05-05  0:09 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 [this message]
2026-05-05 20:16         ` Fernando Fernandez Mancera
2026-05-05 20:17 ` Fernando Fernandez Mancera
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=20260504170912.174235db@kernel.org \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=fmancera@suse.de \
    --cc=hi@alyssa.is \
    --cc=horms@kernel.org \
    --cc=krzk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.