public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Zhengchao Shao <shaozhengchao@huawei•com>
Cc: netdev@vger•kernel.org, dchickles@marvell•com,
	sburla@marvell•com, fmanlunas@marvell•com, davem@davemloft•net,
	edumazet@google•com, kuba@kernel•org, pabeni@redhat•com,
	richardcochran@gmail•com, rvatsavayi@caviumnetworks•com,
	gregkh@linuxfoundation•org, tseewald@gmail•com,
	weiyongjun1@huawei•com, yuehaibing@huawei•com
Subject: Re: [PATCH net v2] net: liquidio: release resources when liquidio driver open failed
Date: Mon, 14 Nov 2022 10:10:15 +0000	[thread overview]
Message-ID: <166842061503.15162.7865291005287723428.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221110103037.133791-1-shaozhengchao@huawei.com>

Hello:

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

On Thu, 10 Nov 2022 18:30:37 +0800 you wrote:
> When liquidio driver open failed, it doesn't release resources. Compile
> tested only.
> 
> Fixes: 5b07aee11227 ("liquidio: MSIX support for CN23XX")
> Fixes: dbc97bfd3918 ("net: liquidio: Add missing null pointer checks")
> Signed-off-by: Zhengchao Shao <shaozhengchao@huawei•com>
> 
> [...]

Here is the summary with links:
  - [net,v2] net: liquidio: release resources when liquidio driver open failed
    https://git.kernel.org/netdev/net/c/8979f428a4af

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 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 10:30 [PATCH net v2] net: liquidio: release resources when liquidio driver open failed Zhengchao Shao
2022-11-10 10:38 ` Leon Romanovsky
2022-11-14 10: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=166842061503.15162.7865291005287723428.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=dchickles@marvell$(echo .)com \
    --cc=edumazet@google$(echo .)com \
    --cc=fmanlunas@marvell$(echo .)com \
    --cc=gregkh@linuxfoundation$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=richardcochran@gmail$(echo .)com \
    --cc=rvatsavayi@caviumnetworks$(echo .)com \
    --cc=sburla@marvell$(echo .)com \
    --cc=shaozhengchao@huawei$(echo .)com \
    --cc=tseewald@gmail$(echo .)com \
    --cc=weiyongjun1@huawei$(echo .)com \
    --cc=yuehaibing@huawei$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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