From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Xiaoliang Yang <xiaoliang.yang_1@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Petr Machata <petrm@nvidia.com>, Ido Schimmel <idosch@nvidia.com>,
Woojung Huh <woojung.huh@microchip.com>,
Oleksij Rempel <linux@rempel-privat.de>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
Hauke Mehrtens <hauke@hauke-m.de>
Subject: Re: [RFC PATCH net-next 1/3] selftests: forwarding: add a vlan_deletion test to bridge_vlan_unaware
Date: Thu, 7 Jul 2022 13:45:34 +0000 [thread overview]
Message-ID: <20220707134533.3abgag7tvf6fdgtz@skbuf> (raw)
In-Reply-To: <CAFBinCCqDRNzeAM2sU2QjJS6WxzCoUi6pwtktE4Th1NTXXNdKg@mail.gmail.com>
On Thu, Jul 07, 2022 at 03:34:07PM +0200, Martin Blumenstingl wrote:
> Hi Vladimir,
>
> On Tue, Jul 5, 2022 at 7:32 PM Vladimir Oltean <vladimir.oltean@nxp.com> wrote:
> [...]
> > .../net/forwarding/bridge_vlan_unaware.sh | 25 ++++++++++++++++---
> > 1 file changed, 22 insertions(+), 3 deletions(-)
> While working on an OpenWrt package for these selftests I found that
> this should be added to the Makefile (in the same directory as the
> test).
> That way it can be installed by a distribution using:
> make -C tools/testing/selftests/net/forwarding/ \
> INSTALL_PATH="some/install/path" \
> install
>
> If you agree then I can also send patches for adding no_forwarding.sh
> and local_termination.sh to that Makefile (which are the only two
> files which are missing currently).
Yes, please do that. I noticed that was the correct way of doing things,
but rsync was enough for my caveman testing so far...
Thanks again for doing this, I haven't forgotten about your other email
and will respond to it later today.
next prev parent reply other threads:[~2022-07-07 13:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 17:31 [RFC PATCH net-next 0/3] Delete ds->configure_vlan_while_not_filtering Vladimir Oltean
2022-07-05 17:31 ` [RFC PATCH net-next 1/3] selftests: forwarding: add a vlan_deletion test to bridge_vlan_unaware Vladimir Oltean
2022-07-07 12:13 ` Ido Schimmel
2022-07-07 13:34 ` Martin Blumenstingl
2022-07-07 13:45 ` Vladimir Oltean [this message]
2022-07-05 17:31 ` [RFC PATCH net-next 2/3] net: dsa: ar9331: remove ds->configure_vlan_while_not_filtering Vladimir Oltean
2022-07-05 17:31 ` [RFC PATCH net-next 3/3] net: dsa: never skip VLAN configuration Vladimir Oltean
2022-07-06 10:51 ` Arun.Ramadoss
2022-07-06 11:12 ` Vladimir Oltean
2022-07-06 16:33 ` Martin Blumenstingl
2022-07-06 16:45 ` Vladimir Oltean
2022-07-06 19:57 ` Martin Blumenstingl
2022-07-07 22:31 ` Vladimir Oltean
2022-07-08 10:00 ` Martin Blumenstingl
2022-07-08 12:09 ` Vladimir Oltean
2022-07-08 22:27 ` Martin Blumenstingl
2022-07-14 10:46 ` Arun.Ramadoss
2022-07-14 15:12 ` Vladimir Oltean
2022-07-15 9:23 ` Arun.Ramadoss
2022-07-15 15:26 ` Vladimir Oltean
2022-07-18 14:34 ` Arun.Ramadoss
2022-07-18 16:24 ` Vladimir Oltean
2022-07-26 15:10 ` Arun.Ramadoss
2022-07-26 17:21 ` Vladimir Oltean
2022-09-12 15:30 ` Arun.Ramadoss
2022-09-12 15:42 ` Vladimir Oltean
2022-09-13 10:57 ` Arun.Ramadoss
2022-09-13 15:09 ` Vladimir Oltean
2022-07-06 20:04 ` Hauke Mehrtens
2022-07-07 22:54 ` Vladimir Oltean
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=20220707134533.3abgag7tvf6fdgtz@skbuf \
--to=vladimir.oltean@nxp.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hauke@hauke-m.de \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux@rempel-privat.de \
--cc=martin.blumenstingl@googlemail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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