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, pabeni@redhat.com,
	netdev@vger.kernel.org, oss-drivers@corigine.com,
	fei.qin@corigine.com
Subject: Re: [PATCH net-next 0/2] nfp: add VEPA and adapter selftest support
Date: Tue, 28 Jun 2022 05:40:15 +0000	[thread overview]
Message-ID: <165639481504.10558.7562272764232611909.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220624073816.1272984-1-simon.horman@corigine.com>

Hello:

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

On Fri, 24 Jun 2022 09:38:14 +0200 you wrote:
> Hi,
> 
> this short series implements two new features in the NFP driver.
> 
> 1. Support for ethtool -t: adapter selftest
> 2. VEPA mode in HW bridge.
>    This supplements existing support for VEB mode.
> 
> [...]

Here is the summary with links:
  - [net-next,1/2] nfp: support vepa mode in HW bridge
    https://git.kernel.org/netdev/net-next/c/be80141108bc
  - [net-next,2/2] nfp: add support for 'ethtool -t DEVNAME' command
    https://git.kernel.org/netdev/net-next/c/15137daef7b0

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



      parent reply	other threads:[~2022-06-28  5:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24  7:38 [PATCH net-next 0/2] nfp: add VEPA and adapter selftest support Simon Horman
2022-06-24  7:38 ` [PATCH net-next 1/2] nfp: support vepa mode in HW bridge Simon Horman
2022-06-24  7:38 ` [PATCH net-next 2/2] nfp: add support for 'ethtool -t DEVNAME' command Simon Horman
2022-06-25  5:43 ` [PATCH net-next 0/2] nfp: add VEPA and adapter selftest support Jakub Kicinski
2022-06-28  5: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=165639481504.10558.7562272764232611909.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=fei.qin@corigine.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=oss-drivers@corigine.com \
    --cc=pabeni@redhat.com \
    --cc=simon.horman@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.