From: patchwork-bot+netdevbpf@kernel.org
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: christopher.lee@cspi.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
gallatin@myri.com, brice@myri.com, jgarzik@redhat.com,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] myri10ge: Fix an error handling path in myri10ge_probe()
Date: Mon, 19 Dec 2022 12:40:16 +0000 [thread overview]
Message-ID: <167145361633.5637.13803811490044949479.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <f03711f1d0919017c081e273e16afd9009874fd4.1671386898.git.christophe.jaillet@wanadoo.fr>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 18 Dec 2022 19:08:40 +0100 you wrote:
> Some memory allocated in myri10ge_probe_slices() is not released in the
> error handling path of myri10ge_probe().
>
> Add the corresponding kfree(), as already done in the remove function.
>
> Fixes: 0dcffac1a329 ("myri10ge: add multislices support")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>
> [...]
Here is the summary with links:
- myri10ge: Fix an error handling path in myri10ge_probe()
https://git.kernel.org/netdev/net/c/d83b950d44d2
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-12-19 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-18 18:08 [PATCH] myri10ge: Fix an error handling path in myri10ge_probe() Christophe JAILLET
2022-12-19 12:40 ` 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=167145361633.5637.13803811490044949479.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=brice@myri.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=christopher.lee@cspi.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gallatin@myri.com \
--cc=jgarzik@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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