From: patchwork-bot+netdevbpf@kernel.org
To: Saeed Mahameed <saeed@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
roid@nvidia.com, saeedm@nvidia.com
Subject: Re: [net 1/2] net/mlx5e: TC, Fix memory leak with rules with internal port
Date: Thu, 30 Dec 2021 02:30:10 +0000 [thread overview]
Message-ID: <164083141032.11132.2786231068394087418.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211229065352.30178-2-saeed@kernel.org>
Hello:
This series was applied to netdev/net.git (master)
by Saeed Mahameed <saeedm@nvidia.com>:
On Tue, 28 Dec 2021 22:53:51 -0800 you wrote:
> From: Roi Dayan <roid@nvidia.com>
>
> Fix a memory leak with decap rule with internal port as destination
> device. The driver allocates a modify hdr action but doesn't set
> the flow attr modify hdr action which results in skipping releasing
> the modify hdr action when releasing the flow.
>
> [...]
Here is the summary with links:
- [net,1/2] net/mlx5e: TC, Fix memory leak with rules with internal port
https://git.kernel.org/netdev/net/c/077cdda764c7
- [net,2/2] net/mlx5e: Fix wrong features assignment in case of error
https://git.kernel.org/netdev/net/c/992d8a4e38f0
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2021-12-30 2:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 6:53 [pull request][net 0/2] mlx5 fixes 2021-12-28 Saeed Mahameed
2021-12-29 6:53 ` [net 1/2] net/mlx5e: TC, Fix memory leak with rules with internal port Saeed Mahameed
2021-12-30 2:30 ` patchwork-bot+netdevbpf [this message]
2021-12-29 6:53 ` [net 2/2] net/mlx5e: Fix wrong features assignment in case of error Saeed Mahameed
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=164083141032.11132.2786231068394087418.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=roid@nvidia.com \
--cc=saeed@kernel.org \
--cc=saeedm@nvidia.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.