[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <877dwn2mja.fsf@mellanox.com>
Date: Thu, 04 Jun 2020 11:44:09 +0200
From: Petr Machata <petrm@...lanox.com>
To: Florian Fainelli <f.fainelli@...il.com>
Cc: Jakub Kicinski <kuba@...nel.org>,
Danielle Ratson <danieller@...lanox.com>,
netdev@...r.kernel.org, davem@...emloft.net,
michael.chan@...adcom.com, jeffrey.t.kirsher@...el.com,
saeedm@...lanox.com, leon@...nel.org, jiri@...lanox.com,
idosch@...lanox.com, snelson@...sando.io, drivers@...sando.io,
andrew@...n.ch, vivien.didelot@...il.com, mlxsw@...lanox.com
Subject: Re: [RFC PATCH net-next 8/8] selftests: net: Add port split test
Florian Fainelli <f.fainelli@...il.com> writes:
> In general there appears to be no direction from kernel maintainers
> about what scripting language is acceptable for writing selftests. My
> concern over time is that if we all let our preferences pick a scripting
> language, we could make it harder for people to actually run these tests
> when running non mainstream systems and we could start requiring more
> and more interpreters or runtime environments over time.
You make it sound as if we pushed like Ruby or SBCL or S-Lang, or some
craziness like that. Python is a conservative choice in the Linux
kernel. Not as conservative as Bash or C, but still conservative, Python
is used quite a bit, even for selftests (TDC!).
Powered by blists - more mailing lists