DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 2/2] app/testpmd: fix MAC endian issue in flow command
Date: Sat, 06 May 2017 10:14:00 +0200	[thread overview]
Message-ID: <2024903.hQifmkdV2L@xps> (raw)
In-Reply-To: <2f565661121fe816a097d41dd375cb7c44932cf4.1493917362.git.adrien.mazarguil@6wind.com>

04/05/2017 19:08, Adrien Mazarguil:
> MAC addresses are implicitly handled in network order since they are
> actually byte strings, however this is not properly enforced with MAC masks
> provided as prefix lengths, which end up inverted on little endian
> systems.
> 
> Fixes: 6df81b325fa4 ("app/testpmd: add items eth/vlan to flow command")
> 
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

Series applies, thanks

      reply	other threads:[~2017-05-06  8:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04 17:08 [dpdk-dev] [PATCH 1/2] app/testpmd: fix stack overwriting by " Adrien Mazarguil
2017-05-04 17:08 ` [dpdk-dev] [PATCH 2/2] app/testpmd: fix MAC endian issue in " Adrien Mazarguil
2017-05-06  8:14   ` Thomas Monjalon [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=2024903.hQifmkdV2L@xps \
    --to=thomas@monjalon.net \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.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).