From: patchwork-bot+netdevbpf@kernel.org
To: Xiongfeng Wang <wangxiongfeng2@huawei.com>
Cc: saeed@kernel.org, sgoutham@marvell.com, lcherian@marvell.com,
gakula@marvell.com, jerinj@marvell.com, hkelam@marvell.com,
sbhatta@marvell.com, davem@davemloft.net, radhac@marvell.com,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
pnalla@marvell.com, snilla@marvell.com, netdev@vger.kernel.org,
yangyingliang@huawei.com
Subject: Re: [PATCH v2] octeontx2-af: Fix reference count issue in rvu_sdp_init()
Date: Thu, 24 Nov 2022 09:10:16 +0000 [thread overview]
Message-ID: <166928101604.31076.14156851234378226224.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123065919.31499-1-wangxiongfeng2@huawei.com>
Hello:
This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 23 Nov 2022 14:59:19 +0800 you wrote:
> pci_get_device() will decrease the reference count for the *from*
> parameter. So we don't need to call put_device() to decrease the
> reference. Let's remove the put_device() in the loop and only decrease
> the reference count of the returned 'pdev' for the last loop because it
> will not be passed to pci_get_device() as input parameter. We don't need
> to check if 'pdev' is NULL because it is already checked inside
> pci_dev_put(). Also add pci_dev_put() for the error path.
>
> [...]
Here is the summary with links:
- [v2] octeontx2-af: Fix reference count issue in rvu_sdp_init()
https://git.kernel.org/netdev/net/c/ad17c2a3f11b
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-11-24 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 6:59 [PATCH v2] octeontx2-af: Fix reference count issue in rvu_sdp_init() Xiongfeng Wang
2022-11-24 9:10 ` 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=166928101604.31076.14156851234378226224.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pnalla@marvell.com \
--cc=radhac@marvell.com \
--cc=saeed@kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=snilla@marvell.com \
--cc=wangxiongfeng2@huawei.com \
--cc=yangyingliang@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.