From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@netronome.com>
Cc: davem@davemloft.net, kuba@kernel.org, louis.peens@corigine.com,
netdev@vger.kernel.org, oss-drivers@netronome.com
Subject: Re: [PATCH net 0/3] Fixes for nfp pre_tunnel code
Date: Tue, 16 Mar 2021 22:50:08 +0000 [thread overview]
Message-ID: <161593500871.15002.14296629686192406959.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210316181310.12199-1-simon.horman@netronome.com>
Hello:
This series was applied to netdev/net.git (refs/heads/master):
On Tue, 16 Mar 2021 19:13:07 +0100 you wrote:
> Louis Peens says:
>
> The following set of patches fixes up a few bugs in the pre_tun
> decap code paths which has been hiding for a while.
>
> Louis Peens (3):
> nfp: flower: fix unsupported pre_tunnel flows
> nfp: flower: add ipv6 bit to pre_tunnel control message
> nfp: flower: fix pre_tun mask id allocation
>
> [...]
Here is the summary with links:
- [net,1/3] nfp: flower: fix unsupported pre_tunnel flows
https://git.kernel.org/netdev/net/c/982e5ee23d76
- [net,2/3] nfp: flower: add ipv6 bit to pre_tunnel control message
https://git.kernel.org/netdev/net/c/5c4f5e19d6a8
- [net,3/3] nfp: flower: fix pre_tun mask id allocation
https://git.kernel.org/netdev/net/c/d8ce0275e45e
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:[~2021-03-16 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 18:13 [PATCH net 0/3] Fixes for nfp pre_tunnel code Simon Horman
2021-03-16 18:13 ` [PATCH net 1/3] nfp: flower: fix unsupported pre_tunnel flows Simon Horman
2021-03-16 18:13 ` [PATCH net 2/3] nfp: flower: add ipv6 bit to pre_tunnel control message Simon Horman
2021-03-16 18:13 ` [PATCH net 3/3] nfp: flower: fix pre_tun mask id allocation Simon Horman
2021-03-16 21:44 ` [PATCH net 0/3] Fixes for nfp pre_tunnel code Jakub Kicinski
2021-03-16 22:50 ` 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=161593500871.15002.14296629686192406959.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--cc=simon.horman@netronome.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.