linux-kernel - Re: [PATCH][GIT PULL][v3.3] ktest: Fix make_min

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1330385574.25686.200.camel@gandalf.stny.rr.com>
Date:	Mon, 27 Feb 2012 18:32:54 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH][GIT PULL][v3.3] ktest: Fix make_min_config test when
 build fails

On Mon, 2012-02-27 at 15:26 -0800, Linus Torvalds wrote:
> On Mon, Feb 27, 2012 at 11:17 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
> >
> > Please pull the latest for-linus tree, which can be found at:
> >
> >  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git
> > ktest-fix-make-min-failed-build
> 
> I'm getting "Already up-to-date" with that tag. It points to your old
> commit be405f95f0a0 ("ktest: Add INGORE_ERRORS to ignore warnings in
> boot up") and normally I'd ask whether you perhaps forgot to push, but
> considering the fairly unique naming of that tag, you clearly *did*
> push.

Crap! I haven't gotten the scripts working yet with the signed tags. It
tagged then merged the latest commit :-p

> 
> Congratulations, you seem to have found a whole new and unique way of
> screwing up ;)

I knew I was good at something!

I'll go fix.

Thanks,

-- Steve

> 
>                Linus "my mom called me 'special' too" Torvalds


--
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/