From: Eelco Chaudron <echaudro@redhat.com>
To: Jun Gu <jun.gu@easystack.cn>
Cc: pshelar@ovn.org, dev@openvswitch.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [ovs-dev] [PATCH net-next] net: openvswitch: Release reference to netdev
Date: Tue, 23 Apr 2024 13:19:01 +0200 [thread overview]
Message-ID: <77015793-E8E4-4AD0-A032-9E0A7F7F0865@redhat.com> (raw)
In-Reply-To: <20240423073751.52706-1-jun.gu@easystack.cn>
On 23 Apr 2024, at 9:37, Jun Gu wrote:
> dev_get_by_name will provide a reference on the netdev. So ensure that
> the reference of netdev is released after completed.
>
> Fixes: 2540088b836f ("net: openvswitch: Check vport netdev name")
> Signed-off-by: Jun Gu <jun.gu@easystack.cn>
Thanks Jun for the follow-up! The change looks good to me!
Acked-by: Eelco Chaudron <echaudro@redhat.com>
next prev parent reply other threads:[~2024-04-23 11:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 7:37 [PATCH net-next] net: openvswitch: Release reference to netdev Jun Gu
2024-04-23 11:15 ` [ovs-dev] " Simon Horman
2024-04-23 11:19 ` Eelco Chaudron [this message]
2024-04-24 15:05 ` Aaron Conole
2024-04-25 0:10 ` patchwork-bot+netdevbpf
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=77015793-E8E4-4AD0-A032-9E0A7F7F0865@redhat.com \
--to=echaudro@redhat.com \
--cc=dev@openvswitch.org \
--cc=jun.gu@easystack.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).