public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Scott Mayhew <smayhew@redhat.com>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: kdevops@lists.linux.dev
Subject: Re: [PATCH] fstests/nfs: add ability to test with NFS loopback mounts
Date: Fri, 6 Sep 2024 08:14:38 -0400	[thread overview]
Message-ID: <ZtryLi-AGk2cD5Hi@aion> (raw)
In-Reply-To: <Zto7Ca8auJg4cANC@bombadil.infradead.org>

On Thu, 05 Sep 2024, Luis Chamberlain wrote:

> On Thu, Sep 05, 2024 at 02:33:54PM -0400, Scott Mayhew wrote:
> > diff --git a/workflows/fstests/nfs/Kconfig b/workflows/fstests/nfs/Kconfig
> > index 6a728aa..eff85c2 100644
> > --- a/workflows/fstests/nfs/Kconfig
> > +++ b/workflows/fstests/nfs/Kconfig
> > @@ -68,6 +68,14 @@ config FSTESTS_NFS_SECTION_TLS
> >  	help
> >  	  Enabling this will test with the xprtsec=tls mount option.
> >  
> > +config FSTESTS_NFS_SECTION_NFSD
> > +	bool "Enable testing section: nfsd"
> 
> You can just add here:
> 
> 	output yaml
> 
> > diff --git a/workflows/fstests/nfs/Makefile b/workflows/fstests/nfs/Makefile
> > index 765f2d3..d76d32a 100644
> > --- a/workflows/fstests/nfs/Makefile
> > +++ b/workflows/fstests/nfs/Makefile
> > @@ -18,6 +18,9 @@ endif
> >  ifeq (y,$(CONFIG_FSTESTS_NFS_SECTION_TLS))
> >  FSTESTS_ARGS += fstests_nfs_section_tls=True
> >  endif
> > +ifeq (y,$(CONFIG_FSTESTS_NFS_SECTION_NFSD))
> > +FSTESTS_ARGS += fstests_nfs_section_nfsd=True
> > +endif
> >  ifeq (y,$(CONFIG_FSTESTS_NFS_SECTION_V42))
> >  FSTESTS_ARGS += fstests_nfs_section_v42=True
> >  endif
> 
> That lets you remove this hunk now that we have yamlconfig support merged.
> 
Nice. I'll do that and give it a test this morning.

-Scott
>   Luis
> 


  reply	other threads:[~2024-09-06 12:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-05 18:33 [PATCH] fstests/nfs: add ability to test with NFS loopback mounts Scott Mayhew
2024-09-05 23:13 ` Luis Chamberlain
2024-09-06 12:14   ` Scott Mayhew [this message]
2024-09-06 14:43 ` Chuck Lever
2024-09-06 15:26   ` Scott Mayhew
2024-09-06 15:29     ` Chuck Lever

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=ZtryLi-AGk2cD5Hi@aion \
    --to=smayhew@redhat.com \
    --cc=kdevops@lists.linux.dev \
    --cc=mcgrof@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