Netdev List
 help / color / mirror / Atom feed
From: Vladimir Oltean <vladimir.oltean@nxp.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-kselftest@vger.kernel.org"
	<linux-kselftest@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"edumazet@google.com" <edumazet@google.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"shuah@kernel.org" <shuah@kernel.org>
Subject: Re: [PATCH 0/2] selftests: forwarding: Install two missing tests
Date: Thu, 7 Jul 2022 22:25:19 +0000	[thread overview]
Message-ID: <20220707222519.movgavbpbptncuu6@skbuf> (raw)
In-Reply-To: <20220707135532.1783925-1-martin.blumenstingl@googlemail.com>

Hi Martin,

On Thu, Jul 07, 2022 at 03:55:30PM +0200, Martin Blumenstingl wrote:
> For some distributions (e.g. OpenWrt) we don't want to rely on rsync
> to copy the tests to the target as some extra dependencies need to be
> installed. The Makefile in tools/testing/selftests/net/forwarding
> already installs most of the tests.
> 
> This series adds the two missing tests to the list of installed tests.
> That way a downstream distribution can build a package using this
> Makefile (and add dependencies there as needed).

Just for future reference, the netdev process is to mark patch sets such
as this one with "PATCH net" since they fix a packaging problem with an
rc kernel. There's more information about this in
Documentation/process/maintainer-netdev.rst.

Do we need to create a Makefile for the selftests symlinked by DSA in
tools/testing/selftests/drivers/net/dsa/, for the symlinks to be
installed, or how do you see this?

The reason why I created the symlinks was to make use of the custom
forwarding.config provided there, and also to reduce the clutter a bit
and only focus on the selftests I felt were relevant for DSA for now.

  parent reply	other threads:[~2022-07-07 22:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07 13:55 [PATCH 0/2] selftests: forwarding: Install two missing tests Martin Blumenstingl
2022-07-07 13:55 ` [PATCH 1/2] selftests: forwarding: Install local_termination.sh Martin Blumenstingl
2022-07-07 22:20   ` Vladimir Oltean
2022-07-07 13:55 ` [PATCH 2/2] selftests: forwarding: Install no_forwarding.sh Martin Blumenstingl
2022-07-07 22:20   ` Vladimir Oltean
2022-07-07 22:25 ` Vladimir Oltean [this message]
2022-07-08 22:28   ` [PATCH 0/2] selftests: forwarding: Install two missing tests Martin Blumenstingl
2022-07-09  3:40 ` patchwork-bot+netdevbpf

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=20220707222519.movgavbpbptncuu6@skbuf \
    --to=vladimir.oltean@nxp.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.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