From: patchwork-bot+netdevbpf@kernel.org
To: Xin Long <lucien.xin@gmail.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
edumazet@google.com, william.xuanziyang@huawei.com
Subject: Re: [PATCH net 0/2] vlan: fix a netdev refcnt leak for QinQ
Date: Wed, 09 Feb 2022 13:40:09 +0000 [thread overview]
Message-ID: <164441400986.27404.8808199212918206130.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1644394642.git.lucien.xin@gmail.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Wed, 9 Feb 2022 03:19:54 -0500 you wrote:
> This issue can be simply reproduced by:
>
> # ip link add dummy0 type dummy
> # ip link add link dummy0 name dummy0.1 type vlan id 1
> # ip link add link dummy0.1 name dummy0.1.2 type vlan id 2
> # rmmod 8021q
>
> [...]
Here is the summary with links:
- [net,1/2] vlan: introduce vlan_dev_free_egress_priority
https://git.kernel.org/netdev/net/c/37aa50c539bc
- [net,2/2] vlan: move dev_put into vlan_dev_uninit
https://git.kernel.org/netdev/net/c/d6ff94afd90b
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-02-09 13:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 8:19 [PATCH net 0/2] vlan: fix a netdev refcnt leak for QinQ Xin Long
2022-02-09 8:19 ` [PATCH net 1/2] vlan: introduce vlan_dev_free_egress_priority Xin Long
2022-02-09 8:19 ` [PATCH net 2/2] vlan: move dev_put into vlan_dev_uninit Xin Long
2022-02-10 1:55 ` Jakub Kicinski
2022-02-10 3:40 ` Xin Long
2022-02-10 5:28 ` Jakub Kicinski
2022-02-10 5:49 ` Eric Dumazet
2022-02-10 5:59 ` Jakub Kicinski
2022-02-11 7:58 ` Xin Long
2022-02-11 22:06 ` Jakub Kicinski
2022-02-10 6:10 ` Eric Dumazet
2022-02-09 13:40 ` 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=164441400986.27404.8808199212918206130.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=william.xuanziyang@huawei.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.