From: patchwork-bot+netdevbpf@kernel.org
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: vburru@marvell.com, aayarekar@marvell.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
sburla@marvell.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH v2 0/2] octeon_ep: Fix the error handling path of octep_request_irqs()
Date: Thu, 19 May 2022 03:10:13 +0000 [thread overview]
Message-ID: <165292981327.2906.8358628971940512633.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1652819974.git.christophe.jaillet@wanadoo.fr>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 May 2022 22:59:43 +0200 you wrote:
> I send a small serie to ease review and because I'm sighly less confident with
> the 2nd patch.
>
> They are related to the same Fixes: tag, so they obviously could be merged if
> it is preferred.
>
> Details on modification of this v2 are given in each patch.
>
> [...]
Here is the summary with links:
- [v2,1/2] octeon_ep: Fix a memory leak in the error handling path of octep_request_irqs()
https://git.kernel.org/netdev/net-next/c/4d3bf6fb5334
- [v2,2/2] octeon_ep: Fix irq releasing in the error handling path of octep_request_irqs()
https://git.kernel.org/netdev/net-next/c/3588c189e45a
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-05-19 3:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 20:59 [PATCH v2 0/2] octeon_ep: Fix the error handling path of octep_request_irqs() Christophe JAILLET
2022-05-17 20:59 ` [PATCH v2 1/2] octeon_ep: Fix a memory leak in " Christophe JAILLET
2022-05-17 20:59 ` [PATCH v2 2/2] octeon_ep: Fix irq releasing " Christophe JAILLET
2022-05-18 5:33 ` [PATCH v2 0/2] octeon_ep: Fix " Dan Carpenter
2022-05-19 3: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=165292981327.2906.8358628971940512633.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aayarekar@marvell.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.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 \
--cc=sburla@marvell.com \
--cc=vburru@marvell.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.