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
Date: Mon, 17 May 2021 12:55:45 +0200 [thread overview]
Message-ID: <20210517105545.GB199206@lothringen> (raw)
In-Reply-To: <20210507202910.GZ975577@paulmck-ThinkPad-P17-Gen-1>
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!
next prev parent reply other threads:[~2021-05-17 10:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 13:15 [PATCH 0/3] torture: Update bare metal config generation Frederic Weisbecker
2021-05-06 13:15 ` [PATCH 1/3] torture: Add --cmdline-to-config parameter to kvm.sh Frederic Weisbecker
2021-05-07 19:20 ` Paul E. McKenney
2021-05-17 10:42 ` Frederic Weisbecker
2021-05-17 20:40 ` Paul E. McKenney
2021-05-06 13:15 ` [PATCH 2/3] torture: Add --configonly parameter for kvm.sh Frederic Weisbecker
2021-05-07 20:29 ` Paul E. McKenney
2021-05-17 10:55 ` Frederic Weisbecker [this message]
2021-05-06 13:15 ` [PATCH 3/3] torture: Update bare metal advices to latest kvm.sh options Frederic Weisbecker
2021-05-07 20:37 ` Paul E. McKenney
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=20210517105545.GB199206@lothringen \
--to=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@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