From: Phil Sutter <phil@nwl.cc>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: netdev@vger.kernel.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2 0/4] add MACsec support
Date: Thu, 14 Apr 2016 16:59:18 +0200 [thread overview]
Message-ID: <20160414145918.GD3715@orbyte.nwl.cc> (raw)
In-Reply-To: <cover.1460622809.git.sd@queasysnail.net>
On Thu, Apr 14, 2016 at 03:01:06PM +0200, Sabrina Dubroca wrote:
> This series introduces support for MACsec devices, with a new device
> type for `ip link`, and a new `ip macsec` subcommand.
>
> The first three patches introduce some necessary helper functions.
>
> Sabrina Dubroca (4):
> utils: make hexstring_a2n provide the number of hex digits parsed
> utils: add get_be{16,32,64}, use them where possible
> utils: provide get_hex to read an hex digit from a char
> ip: add MACsec support
Apart from the unrelated coding-style fix in patch 1 and the somewhat
intricate man page markup:
Acked-by: Phil Sutter <phil@nwl.cc>
next prev parent reply other threads:[~2016-04-14 14:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 13:01 [PATCH iproute2 0/4] add MACsec support Sabrina Dubroca
2016-04-14 13:01 ` [PATCH iproute2 1/4] utils: make hexstring_a2n provide the number of hex digits parsed Sabrina Dubroca
2016-04-14 13:01 ` [PATCH iproute2 2/4] utils: add get_be{16,32,64}, use them where possible Sabrina Dubroca
2016-04-14 13:01 ` [PATCH iproute2 3/4] utils: provide get_hex to read an hex digit from a char Sabrina Dubroca
2016-04-14 13:01 ` [PATCH iproute2 4/4] ip: add MACsec support Sabrina Dubroca
2016-04-14 14:59 ` Phil Sutter [this message]
2016-04-22 16:10 ` [PATCH iproute2 0/4] " Sabrina Dubroca
2016-04-22 16:30 ` Stephen Hemminger
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=20160414145918.GD3715@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=stephen@networkplumber.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).