netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Leon Romanovsky <leon@kernel.org>
Cc: davem@davemloft.net, kuba@kernel.org, leonro@nvidia.com,
	jiri@nvidia.com, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] Two reverts to calm down devlink discussion
Date: Wed, 27 Oct 2021 19:10:07 +0000	[thread overview]
Message-ID: <163536180732.417.12653315027705238824.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1635276828.git.leonro@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Tue, 26 Oct 2021 22:40:40 +0300 you wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Hi,
> 
> Two reverts as was discussed in [1], fast, easy and wrong in long run
> solution to syzkaller bug [2].
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] Revert "devlink: Remove not-executed trap group notifications"
    https://git.kernel.org/netdev/net-next/c/fb9d19c2d844
  - [net-next,2/2] Revert "devlink: Remove not-executed trap policer notifications"
    https://git.kernel.org/netdev/net-next/c/c5e0321e43de

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-27 19:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26 19:40 [PATCH net-next 0/2] Two reverts to calm down devlink discussion Leon Romanovsky
2021-10-26 19:40 ` [PATCH net-next 1/2] Revert "devlink: Remove not-executed trap group notifications" Leon Romanovsky
2021-10-26 19:40 ` [PATCH net-next 2/2] Revert "devlink: Remove not-executed trap policer notifications" Leon Romanovsky
2021-10-27 19: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=163536180732.417.12653315027705238824.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=jiri@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).