From: Jakub Kicinski <kuba@kernel.org>
To: Hangbin Liu <hangbin.liu@linux.dev>
Cc: Ido Schimmel <idosch@nvidia.com>,
Gabriel Goller <g.goller@proxmox.com>,
David Ahern <dsahern@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] ipv6: Add NETCONFA_FORCE_FORWARDING to netconf messages
Date: Tue, 27 Oct 2026 14:38:14 -0700 [thread overview]
Message-ID: <20261027143814.335587dd@kernel.org> (raw)
In-Reply-To: <at7JgfsvrAUxtPzy@fedora>
On Mon, 26 Oct 2026 11:31:13 +0800 Hangbin Liu wrote:
> > This seems to fall under the "Not a regression, not critical" category
> > [1], so can wait for net-next.
Agreed.
I think this is more of a "missing functionality is not a bug", even.
> One question about this rule. For "not critical" fixes, should I make that
> judgment myself and post to net-next? Or should I send them to net and let
> the maintainers decide whether the fix should go into net or net-next?
Post fixes for net, let maintainers decide.
next prev parent reply other threads:[~2026-10-27 21:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 10:59 Gabriel Goller
2026-10-23 11:06 ` netdev-bot+sinfo
2026-10-23 11:15 ` Gabriel Goller
2026-10-25 13:12 ` Ido Schimmel
2026-10-28 10:52 ` Gabriel Goller
2026-10-23 12:12 ` Fernando Fernandez Mancera
2026-10-25 13:11 ` Ido Schimmel
2026-10-26 3:31 ` Hangbin Liu
2026-10-27 21:38 ` Jakub Kicinski [this message]
2026-10-28 0:55 ` Hangbin Liu
2026-10-28 10:55 ` Gabriel Goller
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=20261027143814.335587dd@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@kernel.org \
--cc=g.goller@proxmox.com \
--cc=hangbin.liu@linux.dev \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.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
all inboxes | Powered by JetHome®