Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Mon, 17 May 2021 12:55:45 +0200
From:   Frederic Weisbecker <frederic@kernel.org>
To:     "Paul E. McKenney" <paulmck@kernel.org>
Cc:     LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/3] torture: Add --configonly parameter for kvm.sh
Message-ID: <20210517105545.GB199206@lothringen>
References: <20210506131510.51488-1-frederic@kernel.org>
 <20210506131510.51488-3-frederic@kernel.org>
 <20210507202910.GZ975577@paulmck-ThinkPad-P17-Gen-1>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210507202910.GZ975577@paulmck-ThinkPad-P17-Gen-1>
Precedence: bulk

On Fri, May 07, 2021 at 01:29:10PM -0700, Paul E. McKenney wrote:
> On Thu, May 06, 2021 at 03:15:09PM +0200, Frederic Weisbecker wrote:
> > Those who just want the resulting config file to generate for bare metal
> > don't need to wait for the build. Provide an option to only produce
> > the .config file.
> > 
> > Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
> 
> This one looks good to me, though it depends on 1/3.
> 
> I considered asking for a check of both --configonly and --buildonly,
> but on second thought I just couldn't see the point.  After all, it
> does say why it stopped, either "Config-only run" or "Build-only run"
> and that should suffice.

Ok, I'll resend this one as standalone then so we can think more clearly
on the rest.

Thanks!