From: David Ahern <dsahern@gmail.com>
To: Roman Mashak <mrv@mojatatu.com>
Cc: stephen@networkplumber.org, netdev@vger.kernel.org,
kernel@mojatatu.com, jhs@mojatatu.com, xiyou.wangcong@gmail.com,
jiri@resnulli.us
Subject: Re: [PATCH v2 iproute2-next 1/1] tc: jsonify skbedit action
Date: Sun, 15 Apr 2018 18:11:09 -0600 [thread overview]
Message-ID: <445c0f56-d149-98dc-6a99-66f1443c60f6@gmail.com> (raw)
In-Reply-To: <1523383469-26207-1-git-send-email-mrv@mojatatu.com>
On 4/10/18 12:04 PM, Roman Mashak wrote:
> v2:
> FIxed strings format in print_string()
>
> Signed-off-by: Roman Mashak <mrv@mojatatu.com>
> ---
> tc/m_skbedit.c | 53 +++++++++++++++++++++++++++++------------------------
> 1 file changed, 29 insertions(+), 24 deletions(-)
>
applied to iproute2-next
prev parent reply other threads:[~2018-04-16 0:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 18:04 [PATCH v2 iproute2-next 1/1] tc: jsonify skbedit action Roman Mashak
2018-04-16 0:11 ` David Ahern [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=445c0f56-d149-98dc-6a99-66f1443c60f6@gmail.com \
--to=dsahern@gmail.com \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=kernel@mojatatu.com \
--cc=mrv@mojatatu.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=xiyou.wangcong@gmail.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 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).