From: Jeff Layton <jlayton@kernel.org>
To: kdevops@lists.linux.dev
Subject: [PATCH] fstests: remove the nfs_default guest
Date: Fri, 1 Mar 2024 15:36:10 -0500 [thread overview]
Message-ID: <20240301203610.116647-1-jlayton@kernel.org> (raw)
Chuck recently added an explicit v4.2 guest, which is really the same
thing. Remove the redundant nfs_default guest.
Signed-off-by: Jeff Layton <jlayton@kernel.org>
---
playbooks/roles/fstests/templates/nfs/nfs.config | 5 -----
workflows/fstests/nfs/Kconfig | 10 +---------
2 files changed, 1 insertion(+), 14 deletions(-)
diff --git a/playbooks/roles/fstests/templates/nfs/nfs.config b/playbooks/roles/fstests/templates/nfs/nfs.config
index 3b30114cce62..f301075a8928 100644
--- a/playbooks/roles/fstests/templates/nfs/nfs.config
+++ b/playbooks/roles/fstests/templates/nfs/nfs.config
@@ -10,11 +10,6 @@ SCRATCH_DEV="{{ fstests_nfs_scratch_devpool }}"
RESULT_BASE=$PWD/results/$HOST/$(uname -r)
TEST_DEV={{ fstests_nfs_test_dev }}
CANON_DEVS=yes
-{% if fstests_nfs_section_default -%}
-
-# Test with default mount options
-[nfs_default]
-{% endif %}
{% if fstests_nfs_section_tls -%}
# Test NFS with RPC over TLS
diff --git a/workflows/fstests/nfs/Kconfig b/workflows/fstests/nfs/Kconfig
index 9de5ae04f3a2..f9526b375cf7 100644
--- a/workflows/fstests/nfs/Kconfig
+++ b/workflows/fstests/nfs/Kconfig
@@ -46,14 +46,6 @@ config FSTESTS_NFS_MANUAL_COVERAGE
if FSTESTS_NFS_MANUAL_COVERAGE
-config FSTESTS_NFS_SECTION_DEFAULT
- bool "Enable testing section: nfs_default"
- default y
- help
- Enabling this will test nfs with the default mount options. At the
- time of this writing, this makes the client autonegotiate an NFS
- version, starting with v4.2 if it's available.
-
config FSTESTS_NFS_SECTION_TLS
bool "Enable testing section: nfs_tls"
default n
@@ -63,7 +55,7 @@ config FSTESTS_NFS_SECTION_TLS
config FSTESTS_NFS_SECTION_V42
bool "Enable testing section: nfs_v42"
- default n
+ default y
help
Enabling this will test NFSv4.2.
--
2.43.2
reply other threads:[~2024-03-01 20:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240301203610.116647-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=kdevops@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).