public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: ehakim@nvidia.com
Cc: netdev@vger.kernel.org, raeds@nvidia.com, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	sd@queasysnail.net, atenart@kernel.org
Subject: Re: [PATCH net-next 0/2] Add support to offload macsec using netlink update
Date: Thu, 5 Jan 2023 15:04:42 +0100	[thread overview]
Message-ID: <Y7bY+oYkMojpMCJU@nanopsycho> (raw)
In-Reply-To: <20230105080442.17873-1-ehakim@nvidia.com>

The whole patchset emails, including all patches and coverletter
should be marked with the same version number.


Thu, Jan 05, 2023 at 09:04:40AM CET, ehakim@nvidia.com wrote:
>From: Emeel Hakim <ehakim@nvidia.com>
>
>This series adds support for offloading macsec as part of the netlink
>update routine , command example:
>ip link set link eth2 macsec0 type macsec offload mac
>
>The above is done using the IFLA_MACSEC_OFFLOAD attribute hence
>the second patch of dumping this attribute as part of the macsec
>dump.
>
>Emeel Hakim (2):
>  macsec: add support for IFLA_MACSEC_OFFLOAD in macsec_changelink
>  macsec: dump IFLA_MACSEC_OFFLOAD attribute as part of macsec dump
>
> drivers/net/macsec.c | 127 ++++++++++++++++++++++---------------------
> 1 file changed, 66 insertions(+), 61 deletions(-)
>
>-- 
>2.21.3
>

  parent reply	other threads:[~2023-01-05 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05  8:04 [PATCH net-next 0/2] Add support to offload macsec using netlink update ehakim
2023-01-05  8:04 ` [PATCH net-next v6 1/2] macsec: add support for IFLA_MACSEC_OFFLOAD in macsec_changelink ehakim
2023-01-05  8:04 ` [PATCH net-next v2 2/2] macsec: dump IFLA_MACSEC_OFFLOAD attribute as part of macsec dump ehakim
2023-01-05 14:04 ` Jiri Pirko [this message]
2023-01-05 15:02   ` [PATCH net-next 0/2] Add support to offload macsec using netlink update Emeel Hakim
2023-01-05 15:39     ` Jiri Pirko

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=Y7bY+oYkMojpMCJU@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ehakim@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=raeds@nvidia.com \
    --cc=sd@queasysnail.net \
    /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