All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Simon Horman <simon.horman@corigine.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
	oss-drivers@corigine.com, louis.peens@corigine.com,
	yinjun.zhang@corigine.com
Subject: Re: [PATCH net 0/2] small tc conntrack fixes
Date: Fri, 02 Jul 2021 20:40:04 +0000	[thread overview]
Message-ID: <162525840462.26489.15345953506982982343.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210702092139.25662-1-simon.horman@corigine.com>

Hello:

This series was applied to netdev/net.git (refs/heads/master):

On Fri,  2 Jul 2021 11:21:37 +0200 you wrote:
> Louis Peens says:
> 
> The first patch makes sure that any callbacks registered to
> the ct->nf_tables table are cleaned up before freeing.
> 
> The second patch removes what was effectively a workaround
> in the nfp driver because of the missing cleanup in patch 1.
> 
> [...]

Here is the summary with links:
  - [net,1/2] net/sched: act_ct: remove and free nf_table callbacks
    https://git.kernel.org/netdev/net/c/77ac5e40c44e
  - [net,2/2] nfp: flower-ct: remove callback delete deadlock
    https://git.kernel.org/netdev/net/c/7cc93d888df7

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



      parent reply	other threads:[~2021-07-02 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  9:21 [PATCH net 0/2] small tc conntrack fixes Simon Horman
2021-07-02  9:21 ` [PATCH net 1/2] net/sched: act_ct: remove and free nf_table callbacks Simon Horman
2021-07-02  9:21 ` [PATCH net 2/2] nfp: flower-ct: remove callback delete deadlock Simon Horman
2021-07-02 20: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=162525840462.26489.15345953506982982343.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=louis.peens@corigine.com \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=simon.horman@corigine.com \
    --cc=yinjun.zhang@corigine.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.