From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?Maciej_=C5=BBenczykowski_=3Cmaze=40google=2Ecom=3E?=@ci.codeaurora.org
Cc: zenczykowski@gmail.com, netdev@vger.kernel.org, furry@google.com,
lorenzo@google.com, dsahern@gmail.com, davem@davemloft.net,
edumazet@google.com, yoshfuji@linux-ipv6.org,
stable@vger.kernel.org
Subject: Re: [PATCH net] ipv6: adjust ndisc_is_useropt() to also return true for PIO
Date: Wed, 09 Aug 2023 23:00:22 +0000 [thread overview]
Message-ID: <169162202257.2325.18099698343343735059.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807102533.1147559-1-maze@google.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 7 Aug 2023 03:25:32 -0700 you wrote:
> The upcoming (and nearly finalized):
> https://datatracker.ietf.org/doc/draft-collink-6man-pio-pflag/
> will update the IPv6 RA to include a new flag in the PIO field,
> which will serve as a hint to perform DHCPv6-PD.
>
> As we don't want DHCPv6 related logic inside the kernel, this piece of
> information needs to be exposed to userspace. The simplest option is to
> simply expose the entire PIO through the already existing mechanism.
>
> [...]
Here is the summary with links:
- [net] ipv6: adjust ndisc_is_useropt() to also return true for PIO
https://git.kernel.org/netdev/net/c/048c796beb6e
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-08-09 23:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 10:25 [PATCH net] ipv6: adjust ndisc_is_useropt() to also return true for PIO Maciej Żenczykowski
2023-08-09 23:00 ` 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=169162202257.2325.18099698343343735059.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?Maciej_=C5=BBenczykowski_=3Cmaze=40google=2Ecom=3E?=@ci.codeaurora.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=edumazet@google.com \
--cc=furry@google.com \
--cc=lorenzo@google.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.org \
--cc=zenczykowski@gmail.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