From: Fernando Fernandez Mancera <fmancera@suse.de>
To: patchwork-bot+netdevbpf@kernel.org
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
fgont@si6networks.com
Subject: Re: [PATCH net v2] ipv6: addrconf: reduce default temp_valid_lft to 2 days
Date: Fri, 20 Feb 2026 16:39:27 +0100 [thread overview]
Message-ID: <b3466d97-cbd2-4288-8da4-9f30df1ae477@suse.de> (raw)
In-Reply-To: <177137761857.765825.5185653389299397165.git-patchwork-notify@kernel.org>
On 2/18/26 2:20 AM, patchwork-bot+netdevbpf@kernel.org wrote:
> Hello:
>
> This patch was applied to netdev/net.git (main)
> by Jakub Kicinski <kuba@kernel.org>:
>
> On Sat, 14 Feb 2026 18:25:43 +0100 you wrote:
>> This is a recommendation from RFC 8981 and it was intended to be changed
>> by commit 969c54646af0 ("ipv6: Implement draft-ietf-6man-rfc4941bis")
>> but it only changed the sysctl documentation.
>>
>> Fixes: 969c54646af0 ("ipv6: Implement draft-ietf-6man-rfc4941bis")
>> Signed-off-by: Fernando Fernandez Mancera <fmancera@suse.de>
>>
>> [...]
>
> Here is the summary with links:
> - [net,v2] ipv6: addrconf: reduce default temp_valid_lft to 2 days
> https://git.kernel.org/netdev/net/c/9e371b0ba7f5
>
FTR; the patch was merged without the fixes tag. I think it would be
good to backport this to stable kernels because otherwise the
documentation and the real configured value are contradicting each other.
> You are awesome, thank you!
next prev parent reply other threads:[~2026-02-20 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 17:25 [PATCH net v2] ipv6: addrconf: reduce default temp_valid_lft to 2 days Fernando Fernandez Mancera
2026-02-15 9:34 ` Eric Dumazet
2026-02-18 1:20 ` patchwork-bot+netdevbpf
2026-02-20 15:39 ` Fernando Fernandez Mancera [this message]
2026-02-20 20:28 ` Jakub Kicinski
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=b3466d97-cbd2-4288-8da4-9f30df1ae477@suse.de \
--to=fmancera@suse.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fgont@si6networks.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=patchwork-bot+netdevbpf@kernel.org \
/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