All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, kuba@kernel.org,
	simon.horman@corigine.com, shuah@kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/2] add MACsec offload selftests
Date: Fri, 14 Jul 2023 08:20:20 +0000	[thread overview]
Message-ID: <168932282082.1632.13701675853325201374.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1689173906.git.sd@queasysnail.net>

Hello:

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

On Thu, 13 Jul 2023 15:20:22 +0200 you wrote:
> Patch 1 adds MACsec offload to netdevsim (unchanged from v2).
> 
> Patch 2 adds a corresponding selftest to the rtnetlink testsuite.
> 
> Sabrina Dubroca (2):
>   netdevsim: add dummy macsec offload
>   selftests: rtnetlink: add MACsec offload tests
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/2] netdevsim: add dummy macsec offload
    https://git.kernel.org/netdev/net-next/c/02b34d03a24b
  - [net-next,v3,2/2] selftests: rtnetlink: add MACsec offload tests
    https://git.kernel.org/netdev/net-next/c/3b5222e2ac57

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



      parent reply	other threads:[~2023-07-14  8:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 13:20 [PATCH net-next v3 0/2] add MACsec offload selftests Sabrina Dubroca
2023-07-13 13:20 ` [PATCH net-next v3 1/2] netdevsim: add dummy macsec offload Sabrina Dubroca
2023-07-13 13:20 ` [PATCH net-next v3 2/2] selftests: rtnetlink: add MACsec offload tests Sabrina Dubroca
2023-07-14  8:20 ` 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=168932282082.1632.13701675853325201374.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sd@queasysnail.net \
    --cc=shuah@kernel.org \
    --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.