From: David Miller <davem@davemloft.net>
To: petrm@mellanox.com
Cc: netdev@vger.kernel.org, idosch@mellanox.com
Subject: Re: [PATCH net-next 0/2] mlxsw: Test coverage for DSCP leftover fix
Date: Wed, 31 Jul 2019 08:47:26 -0700 (PDT) [thread overview]
Message-ID: <20190731.084726.1953796309631404531.davem@davemloft.net> (raw)
In-Reply-To: <cover.1564568595.git.petrm@mellanox.com>
From: Petr Machata <petrm@mellanox.com>
Date: Wed, 31 Jul 2019 10:30:25 +0000
> This patch set fixes some global scope pollution issues in the DSCP tests
> (in patch #1), and then proceeds (in patch #2) to add a new test for
> checking whether, after DSCP prioritization rules are removed from a port,
> DSCP rewrites consistently to zero, instead of the last removed rule still
> staying in effect.
Series applied.
prev parent reply other threads:[~2019-07-31 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 10:30 [PATCH net-next 0/2] mlxsw: Test coverage for DSCP leftover fix Petr Machata
2019-07-31 10:30 ` [PATCH net-next 1/2] selftests: mlxsw: Fix local variable declarations in DSCP tests Petr Machata
2019-07-31 10:30 ` [PATCH net-next 2/2] selftests: mlxsw: Add a test for leftover DSCP rule Petr Machata
2019-07-31 15:47 ` David Miller [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=20190731.084726.1953796309631404531.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@mellanox.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).