linux-kernel - [PATCH 0/2] [GIT PULL] ktest: A couple of fixes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20120502004439.965120020@goodmis.org>
Date:	Tue, 01 May 2012 20:44:39 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: [PATCH 0/2] [GIT PULL] ktest: A couple of fixes

Linus,

This includes two fixes, one of which seems to have fell under your
radar before:

 http://groups.google.com/group/linux.kernel/browse_thread/thread/b0a0880f3e0f415a/188f12ab40b7a6c9?show_docid=188f12ab40b7a6c9

But that's fine, as I pulled in Russ's patch after merging your tree,
and it did not do a fast forward of your tree. I didn't notices that
it did that, and it seemed a bit strange to do a commit for a fast
forward.

Is git set up to not fast forward by default? (I need to give it another try)

Anyway, changed my tree to be a fast forward (you haven't pulled it
yet, so no harm done with a rebase), and I added another fix.

New signed tag.

Please pull the latest ktest-for-v3.4-rc5 tree, which can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
ktest-for-v3.4-rc5

Head SHA1: b66786c7ff4441f0b9ac3b05f8e62cad75df65ff

Russ Dill (1):
      ktest.pl: Fix combined usage of BISECT_REVERSE and BISECT_SKIP

Steven Rostedt (1):
      ktest: Fix reboot on success stopping all reboots

----
 tools/testing/ktest/ktest.pl |   12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/