mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: John Kacur <jkacur@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 3/6] ktest: Reboot to good kernel after every bisect run
Date: Mon, 23 May 2011 11:18:04 -0400	[thread overview]
Message-ID: <1306163884.1465.38.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <BANLkTimtR=_X=4hWgagtRiawHH_59V7PVQ@mail.gmail.com>

On Mon, 2011-05-23 at 17:04 +0200, John Kacur wrote:
> On Mon, May 23, 2011 at 3:51 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
> > From: Steven Rostedt <srostedt@redhat.com>
> >
> > Reboot after each bisect run regardless if the bisect passed
> > or failed. The test may just be to boot the kernel and that kernel
> > may not have a way to copy the next kerne to it. Reboot to a known
> > good kernel after each bisect run.
> >
> 
> How about an option to not reboot for good kernels?

Would be trivial to add. But that would be for 2.6.41.

Thanks,

-- Steve



  reply	other threads:[~2011-05-23 15:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 13:51 [PATCH 0/6] ktest: Updates for ktest.pl Steven Rostedt
2011-05-23 13:51 ` [PATCH 1/6] ktest: Fix post install command Steven Rostedt
2011-05-23 13:51 ` [PATCH 2/6] ktest: If test failed due to timeout, print that Steven Rostedt
2011-05-23 13:51 ` [PATCH 3/6] ktest: Reboot to good kernel after every bisect run Steven Rostedt
2011-05-23 15:04   ` John Kacur
2011-05-23 15:18     ` Steven Rostedt [this message]
2011-05-23 13:51 ` [PATCH 4/6] ktest: Reboot after each patchcheck run Steven Rostedt
2011-05-23 13:51 ` [PATCH 5/6] ktest: Create variables for the ktest config files Steven Rostedt
2011-05-23 13:51 ` [PATCH 6/6] ktest: Allow options to be used by other options Steven Rostedt

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=1306163884.1465.38.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=jkacur@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®