I need to ask the following question to the Linux kernel community as
the AX25 amateur radio community is already having to
work around a few broken commits that were committed 4.1.22+:
Is anyone actually _*testing*_ these proposed changes to make sure
the AX.25 and related ecosystem still
so I can better understand if it makes sense to add tests there? For
example, do you know if it's "changed based" so only certain tests will
run if given files are updated?
--David
KI6ZHD
On 10/28/2017 06:45 PM, David Miller wrote:
From: David Ranch
Date: Sat, 28 Oct 2017 10:
ith WAY too much noise for various development
areas.
Does anyone else have thoughts on this topic?
--David
KI6ZHD
On 10/27/2017 12:48 PM, Gustavo A. R. Silva wrote:
Hi David,
Quoting David Ranch :
Hello Gustavo,
I appreciate you working on keeping up the kernel and maintaining some
of the olde
Hello Gustavo,
I appreciate you working on keeping up the kernel and maintaining some
of the older feature areas like AX.25, Netrom, etc. Other than auditing
your code changes, can you tell me what you're changing? I've been
attempting to find who / where does regression tests for the Linus
Hello David,
Unless I'm doing something wrong, it seems this patch has only been
applied to the newest
kernel:
Git/linux-stable$ git tag -l --contains
4a7d99ea1b27734558feb6833f180cd38a159940
v4.7-rc6
How can we get this critical fix applied to the other stable kernel
versions? I w
Hello David,
I don't have a specific commit # for you at the moment but there have been a
few serious regressions since 4.1.x. When new code gets commited, are there
any systems to run regession tests on? I'd be willing to build up a pair of
VMs that can be run with scripts to verify say basi
