From: patchwork-bot+netdevbpf@kernel.org
To: Peilin Ye <yepeilin.cs@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, eric.dumazet@gmail.com,
yoshfuji@linux-ipv6.org, dsahern@kernel.org, pabeni@redhat.com,
peilin.ye@bytedance.com, u9012063@gmail.com,
cong.wang@bytedance.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 net-next 0/2] ip_gre, ip6_gre: Make [IP6]GRE[TAP] devices always NETIF_F_LLTX
Date: Mon, 02 May 2022 08:50:11 +0000 [thread overview]
Message-ID: <165148141150.15603.6013828424005630453.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1651207788.git.peilin.ye@bytedance.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Thu, 28 Apr 2022 22:24:17 -0700 you wrote:
> From: Peilin Ye <peilin.ye@bytedance.com>
>
> v1: https://lore.kernel.org/netdev/cover.1650580763.git.peilin.ye@bytedance.com/
>
> change since v1:
> - deleted "depends on patch..." in [1/2]'s commit message
>
> [...]
Here is the summary with links:
- [v2,net-next,1/2] ip_gre: Make GRE and GRETAP devices always NETIF_F_LLTX
https://git.kernel.org/netdev/net-next/c/020e8f60aa8b
- [v2,net-next,2/2] ip6_gre: Make IP6GRE and IP6GRETAP devices always NETIF_F_LLTX
https://git.kernel.org/netdev/net-next/c/b11ebf2ca2c1
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:[~2022-05-02 8:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 5:24 [PATCH v2 net-next 0/2] ip_gre, ip6_gre: Make [IP6]GRE[TAP] devices always NETIF_F_LLTX Peilin Ye
2022-04-29 5:25 ` [PATCH v2 net-next 1/2] ip_gre: Make GRE and GRETAP " Peilin Ye
2022-04-29 5:25 ` [PATCH v2 net-next 2/2] ip6_gre: Make IP6GRE and IP6GRETAP " Peilin Ye
2022-05-02 8: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=165148141150.15603.6013828424005630453.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cong.wang@bytedance.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peilin.ye@bytedance.com \
--cc=u9012063@gmail.com \
--cc=yepeilin.cs@gmail.com \
--cc=yoshfuji@linux-ipv6.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