All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 616] [mlx5] packet does not match a corresponding rte_flow rule due to inner ether_type spec validation
Date: Wed, 20 Jan 2021 08:29:04 +0000	[thread overview]
Message-ID: <bug-616-3-zxwEqMEH4l@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-616-3@http.bugs.dpdk.org/>

https://bugs.dpdk.org/show_bug.cgi?id=616

Asaf Penso (asafp@nvidia.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
                 CC|                            |asafp@nvidia.com
         Resolution|---                         |WONTFIX

--- Comment #2 from Asaf Penso (asafp@nvidia.com) ---
Appears also in the previous 18.11 LTS versions and there were no issues from
users.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      reply	other threads:[~2021-01-20  8:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 13:54 [dpdk-dev] [Bug 616] [mlx5] packet does not match a corresponding rte_flow rule due to inner ether_type spec validation bugzilla
2021-01-20  8:29 ` bugzilla [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=bug-616-3-zxwEqMEH4l@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 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.