From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=91.218.175.13 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1793148971; b=JZxTJtF54aNrovaqXjvKHhxGZ4x01zR5Yf0WhRN11Z+9RT+Pon5Rx3+0aSqo4+xkQVqr 0YszNcWi5FgWCooPkf4tRN0vr2cqhTCr48rSu8IqWGBR4WYxTV1Ubs0OGhPvPZPiK4UID yBFRun3aUYjPUBl3uuGuqtwAzBtt/gJN0WliorqOlPm7DjyN0hWPoQdabnf5uGqgWcMJ6 2BkLNwkzJssnK27qdKt+hiFq47fWWQlzgPR+qXHbzhq3RfVvr9cEA9gqxmzTjh43IXCtt La34lXMu5COywAJ+qz4R7FbwE+Kf/qnnX4jOYeBknFY8APwJRYjN1/tweUabScms0SA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1793148971; h=DMARC-Filter:X-Envelope-To:DKIM-Signature:X-Envelope-To:Received: X-Mizu-Trace-ID:X-Migadu-Flow:Date:From:To:Cc:Subject:Message-ID: References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To; bh=eit43aTmntcI/a8LLYb0KjYLZEdX3ZZM9XTb1U4DSis=; b=C0JdSe39F27ob24Z4okSwyDi0/pxpkMLeziaITvvuAxsg/PycIurDomnrRUbUwrorDd8 Rn2WS/gmZVZUOEF0NPzgBFmuSjtMGl3qN6u31cEFr/WW6HAwz8rSUF6xdrFRj7Px4Vnjm tTxkcK5x1XIR2uptHXrMGmyk6HDpio0Rpk5IQpzCT7oYm4igtrsI1UJSdxlV/1uvTpg+s 0e9ansB21fUbhRlZnp3qLTyhtUw7XFipGo4aQ4xUJbysRUpt2vOksNCvNeRd7fdqsYl1y 7+EU9KTsNl6XSkjJbHDPKICgWHTr9jAROenWVWDaDnp7Hm84uKMsT9yfvxiqHpn/dmQ== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dmarc=pass header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass header.d=linux.dev header.i=@linux.dev header.a=rsa-sha256 header.s=key1 header.b=la24EeBL; arc=none smtp.remote-ip=91.218.175.13 Received: from mta0.migadu.com (out-13.mta0.migadu.com [91.218.175.13]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D02C2606A31E for ; Wed, 28 Oct 2026 00:56:04 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.2 smtp.subspace.kernel.org D02C2606A31E Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key, unprotected) header.d=linux.dev header.i=@linux.dev header.a=rsa-sha256 header.s=key1 header.b=la24EeBL X-Envelope-To: linux-kernel@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=jD/DZc8I3oxbxEmjOJOmyZnS5g2so0+XNRCpAsgTwH8=; c=simple/simple; d=linux.dev; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1793148963; v=1; x=1793753763; b=la24EeBLCP2x6FcVGepMMGQhXvIelV/QsM8FWqPyAOvhzD1KRXt5FglTaSJiF6FZcJTRreP4 WsVut+10jGPoFfWHyzZlAMmz2LvRMuWLUDP9VEOZQ6+g7NyPnTFp7/eakdeSuMxVuIA5IOEKdIa lw6WFecjU1vZN98aU9lTwGIg= X-Envelope-To: linux-kernel@vger.kernel.org Received: by mta11.migadu.com with ESMTPS id 9002972c6cdf6e23; Wed, 28 Oct 2026 00:56:03 +0000 X-Mizu-Trace-ID: 9002972c6cdf6e23 X-Migadu-Flow: FLOW_OUT Date: Wed, 28 Oct 2026 08:55:54 +0800 From: Hangbin Liu To: Jakub Kicinski Cc: Ido Schimmel , Gabriel Goller , David Ahern , "David S. Miller" , Eric Dumazet , Paolo Abeni , Simon Horman , Nicolas Dichtel , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net] ipv6: Add NETCONFA_FORCE_FORWARDING to netconf messages Message-ID: References: <20261023-ipv6_add_netconfa-v1-1-94d14b07d621@proxmox.com> <20261025131102.GA184152@shredder> <20261027143814.335587dd@kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20261027143814.335587dd@kernel.org> On Tue, Oct 27, 2026 at 02:38:14PM -0700, Jakub Kicinski wrote: > 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. Good to know this. Thanks for your reply. Regards Hangbin