All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Yang Yingliang <yangyingliang@huawei.com>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	davem@davemloft.net, kuba@kernel.org, andrew@aj.id.au,
	gwshan@linux.vnet.ibm.com
Subject: Re: [PATCH -next] net: ftgmac100: add missing error return code in ftgmac100_probe()
Date: Mon, 24 May 2021 00:30:11 +0000	[thread overview]
Message-ID: <162181621137.30453.7620078087763802418.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210522120246.1125535-1-yangyingliang@huawei.com>

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Sat, 22 May 2021 20:02:46 +0800 you wrote:
> The variables will be free on path err_phy_connect, it should
> return error code, or it will cause double free when calling
> ftgmac100_remove().
> 
> Fixes: bd466c3fb5a4 ("net/faraday: Support NCSI mode")
> Fixes: 39bfab8844a0 ("net: ftgmac100: Add support for DT phy-handle property")
> Reported-by: Hulk Robot <hulkci@huawei.com>
> Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
> 
> [...]

Here is the summary with links:
  - [-next] net: ftgmac100: add missing error return code in ftgmac100_probe()
    https://git.kernel.org/netdev/net-next/c/52af13a41489

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



      reply	other threads:[~2021-05-24  0:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 12:02 [PATCH -next] net: ftgmac100: add missing error return code in ftgmac100_probe() Yang Yingliang
2021-05-24  0:30 ` 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=162181621137.30453.7620078087763802418.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@aj.id.au \
    --cc=davem@davemloft.net \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --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.