netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: cuigaosheng <cuigaosheng1@huawei.com>
Cc: michael.chan@broadcom.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	gospo@broadcom.com, netdev@vger.kernel.org
Subject: Re: [PATCH net] bnxt_en: Remove debugfs when pci_register_driver failed
Date: Mon, 14 Nov 2022 11:00:15 +0000	[thread overview]
Message-ID: <166842361544.12717.8041428660747446249.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221111070433.3498215-1-cuigaosheng1@huawei.com>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 11 Nov 2022 15:04:33 +0800 you wrote:
> When pci_register_driver failed, we need to remove debugfs,
> which will caused a resource leak, fix it.
> 
> Resource leak logs as follows:
> [   52.184456] debugfs: Directory 'bnxt_en' with parent '/' already present!
> 
> Fixes: cabfb09d87bd ("bnxt_en: add debugfs support for DIM")
> Signed-off-by: Gaosheng Cui <cuigaosheng1@huawei.com>
> 
> [...]

Here is the summary with links:
  - [net] bnxt_en: Remove debugfs when pci_register_driver failed
    https://git.kernel.org/netdev/net/c/991aef4ee4f6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-11-14 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  7:04 [PATCH net] bnxt_en: Remove debugfs when pci_register_driver failed Gaosheng Cui
2022-11-13  8:02 ` Leon Romanovsky
2022-11-13 19:25 ` Michael Chan
2022-11-14 11:00 ` 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=166842361544.12717.8041428660747446249.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=cuigaosheng1@huawei.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gospo@broadcom.com \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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 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 NNTP newsgroup(s).