netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Andrew Lunn <andrew@lunn.ch>, Vladimir Oltean <olteanv@gmail.com>,
	Claudiu Manoil <claudiu.manoil@nxp.com>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	UNGLinuxDriver@microchip.com,
	Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
	Colin Foster <colin.foster@in-advantage.com>
Subject: Re: [PATCH net-next 0/3] Streamline the tc_flower_chains Ocelot selftest
Date: Tue, 3 May 2022 17:53:41 -0700	[thread overview]
Message-ID: <20220503175341.661d6e4d@kernel.org> (raw)
In-Reply-To: <20220503124332.857499-1-vladimir.oltean@nxp.com>

On Tue,  3 May 2022 15:43:29 +0300 Vladimir Oltean wrote:
> The forwarding selftest framework has conventions for the test output
> format, interface names and order. The driver-specific tc_flower_chains.sh
> follows none of those conventions. This change set addresses that.

Both of the 3-patch series did not apply at the time of posting :(

      parent reply	other threads:[~2022-05-04  0:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-03 12:43 [PATCH net-next 0/3] Streamline the tc_flower_chains Ocelot selftest Vladimir Oltean
2022-05-03 12:43 ` [PATCH net-next 1/3] selftests: ocelot: tc_flower_chains: streamline test output Vladimir Oltean
2022-05-03 12:43 ` [PATCH net-next 2/3] selftests: ocelot: tc_flower_chains: use conventional interface names Vladimir Oltean
2022-05-03 12:43 ` [PATCH net-next 3/3] selftests: ocelot: tc_flower_chains: reorder interfaces Vladimir Oltean
2022-05-04  0:53 ` Jakub Kicinski [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=20220503175341.661d6e4d@kernel.org \
    --to=kuba@kernel.org \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=claudiu.manoil@nxp.com \
    --cc=colin.foster@in-advantage.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=vivien.didelot@gmail.com \
    --cc=vladimir.oltean@nxp.com \
    --cc=xiaoliang.yang_1@nxp.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).