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, yinjun.zhang@corigine.com,
	louis.peens@corigine.com
Subject: Re: [PATCH net 0/2] nfp: fix bugs caused by adaptive coalesce
Date: Fri, 29 Oct 2021 12:50:08 +0000	[thread overview]
Message-ID: <163551180838.32606.5927261985281379723.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211029112903.16806-1-simon.horman@corigine.com>

Hello:

This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 29 Oct 2021 13:29:01 +0200 you wrote:
> Hi,
> 
> this series contains fixes for two bugs introduced when
> when adaptive coalesce support was added to the NFP driver in
> v5.15 by 9d32e4e7e9e1 ("nfp: add support for coalesce adaptive feature")
> 
> Yinjun Zhang (2):
>   nfp: fix NULL pointer access when scheduling dim work
>   nfp: fix potential deadlock when canceling dim work
> 
> [...]

Here is the summary with links:
  - [net,1/2] nfp: fix NULL pointer access when scheduling dim work
    https://git.kernel.org/netdev/net/c/f8d384a640dd
  - [net,2/2] nfp: fix potential deadlock when canceling dim work
    https://git.kernel.org/netdev/net/c/17e712c6a1ba

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-10-29 12:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 11:29 [PATCH net 0/2] nfp: fix bugs caused by adaptive coalesce Simon Horman
2021-10-29 11:29 ` [PATCH net 1/2] nfp: fix NULL pointer access when scheduling dim work Simon Horman
2021-10-29 11:29 ` [PATCH net 2/2] nfp: fix potential deadlock when canceling " Simon Horman
2021-10-29 12:50 ` 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=163551180838.32606.5927261985281379723.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.