netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Zhengchao Shao <shaozhengchao@huawei.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com,
	u.kleine-koenig@pengutronix.de, mkl@pengutronix.de,
	tie-fei.zang@freescale.com, akpm@osdl.org,
	Alexandre.Bounine@tundra.com, jeff@garzik.org,
	weiyongjun1@huawei.com, yuehaibing@huawei.com
Subject: Re: [PATCH net] ethernet: tundra: free irq when alloc ring failed in tsi108_open()
Date: Thu, 10 Nov 2022 14:50:16 +0000	[thread overview]
Message-ID: <166809181644.19446.17796054379922297887.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221109044016.126866-1-shaozhengchao@huawei.com>

Hello:

This patch was applied to netdev/net.git (master)
by Paolo Abeni <pabeni@redhat.com>:

On Wed, 9 Nov 2022 12:40:16 +0800 you wrote:
> When alloc tx/rx ring failed in tsi108_open(), it doesn't free irq. Fix
> it.
> 
> Fixes: 5e123b844a1c ("[PATCH] Add tsi108/9 On Chip Ethernet device driver support")
> Signed-off-by: Zhengchao Shao <shaozhengchao@huawei.com>
> ---
> v2: move free_irq to error handling path and modify fixes tag
> 
> [...]

Here is the summary with links:
  - [net] ethernet: tundra: free irq when alloc ring failed in tsi108_open()
    https://git.kernel.org/netdev/net/c/acce40037041

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



      reply	other threads:[~2022-11-10 14:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-09  4:40 [PATCH net] ethernet: tundra: free irq when alloc ring failed in tsi108_open() Zhengchao Shao
2022-11-10 14:50 ` 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=166809181644.19446.17796054379922297887.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=Alexandre.Bounine@tundra.com \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jeff@garzik.org \
    --cc=kuba@kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shaozhengchao@huawei.com \
    --cc=tie-fei.zang@freescale.com \
    --cc=u.kleine-koenig@pengutronix.de \
    --cc=weiyongjun1@huawei.com \
    --cc=yuehaibing@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 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).