netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	willemb@google.com, liu3101@purdue.edu
Subject: Re: [PATCH net v2] ipv6: per-netns exclusive flowlabel checks
Date: Thu, 17 Feb 2022 05:20:10 +0000	[thread overview]
Message-ID: <164507521091.4843.2205863752404721765.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220215160037.1976072-1-willemdebruijn.kernel@gmail.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 15 Feb 2022 11:00:37 -0500 you wrote:
> From: Willem de Bruijn <willemb@google.com>
> 
> Ipv6 flowlabels historically require a reservation before use.
> Optionally in exclusive mode (e.g., user-private).
> 
> Commit 59c820b2317f ("ipv6: elide flowlabel check if no exclusive
> leases exist") introduced a fastpath that avoids this check when no
> exclusive leases exist in the system, and thus any flowlabel use
> will be granted.
> 
> [...]

Here is the summary with links:
  - [net,v2] ipv6: per-netns exclusive flowlabel checks
    https://git.kernel.org/netdev/net/c/0b0dff5b3b98

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2022-02-17  5:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 16:00 [PATCH net v2] ipv6: per-netns exclusive flowlabel checks Willem de Bruijn
2022-02-17  5:20 ` 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=164507521091.4843.2205863752404721765.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=liu3101@purdue.edu \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.com \
    --cc=willemdebruijn.kernel@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;
as well as URLs for NNTP newsgroup(s).