From: patchwork-bot+netdevbpf@kernel.org
To: Alex Henrie <alexhenrie24@gmail.com>
Cc: netdev@vger.kernel.org, jbohac@suse.cz,
benoit.boissinot@ens-lyon.org, davem@davemloft.net,
hideaki.yoshifuji@miraclelinux.com, dsahern@kernel.org,
pabeni@redhat.com, kuba@kernel.org
Subject: Re: [PATCH net-next v2 0/4] net: ipv6/addrconf: ensure that temporary addresses' preferred lifetimes are in the valid range
Date: Thu, 26 Oct 2023 01:30:26 +0000 [thread overview]
Message-ID: <169828382626.14693.5307000504345152936.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231024212312.299370-1-alexhenrie24@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 24 Oct 2023 15:23:06 -0600 you wrote:
> No changes from v2, but there are only four patches now because the
> first patch has already been applied.
>
> https://lore.kernel.org/all/20230829054623.104293-1-alexhenrie24@gmail.com/
>
> Alex Henrie (4):
> net: ipv6/addrconf: clamp preferred_lft to the maximum allowed
> net: ipv6/addrconf: clamp preferred_lft to the minimum required
> Documentation: networking: explain what happens if temp_valid_lft is
> too small
> Documentation: networking: explain what happens if temp_prefered_lft
> is too small or too large
>
> [...]
Here is the summary with links:
- [net-next,v2,1/4] net: ipv6/addrconf: clamp preferred_lft to the maximum allowed
https://git.kernel.org/netdev/net-next/c/bfbf81b31093
- [net-next,v2,2/4] net: ipv6/addrconf: clamp preferred_lft to the minimum required
https://git.kernel.org/netdev/net-next/c/629df6701c8a
- [net-next,v2,3/4] Documentation: networking: explain what happens if temp_valid_lft is too small
https://git.kernel.org/netdev/net-next/c/433d6c8048cb
- [net-next,v2,4/4] Documentation: networking: explain what happens if temp_prefered_lft is too small or too large
https://git.kernel.org/netdev/net-next/c/ec575f885e3e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-26 1:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 21:23 [PATCH net-next v2 0/4] net: ipv6/addrconf: ensure that temporary addresses' preferred lifetimes are in the valid range Alex Henrie
2023-10-24 21:23 ` [PATCH net-next v2 1/4] net: ipv6/addrconf: clamp preferred_lft to the maximum allowed Alex Henrie
2023-10-25 12:23 ` Jiri Pirko
2023-10-25 16:28 ` Alex Henrie
2023-10-26 5:11 ` Jiri Pirko
2023-10-26 0:41 ` David Ahern
2023-10-24 21:23 ` [PATCH net-next v2 2/4] net: ipv6/addrconf: clamp preferred_lft to the minimum required Alex Henrie
2023-10-25 12:25 ` Jiri Pirko
2023-10-26 0:43 ` David Ahern
2023-10-24 21:23 ` [PATCH net-next v2 3/4] Documentation: networking: explain what happens if temp_valid_lft is too small Alex Henrie
2023-10-26 0:43 ` David Ahern
2023-10-24 21:23 ` [PATCH net-next v2 4/4] Documentation: networking: explain what happens if temp_prefered_lft is too small or too large Alex Henrie
2023-10-26 0:44 ` David Ahern
2023-10-26 1:30 ` patchwork-bot+netdevbpf [this message]
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=169828382626.14693.5307000504345152936.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexhenrie24@gmail.com \
--cc=benoit.boissinot@ens-lyon.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=hideaki.yoshifuji@miraclelinux.com \
--cc=jbohac@suse.cz \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).