linux-kernel - Re: linux-next: build warning after merge of the tip tree

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: <20161214191043.680ca964@canb.auug.org.au>
Date:   Wed, 14 Dec 2016 19:10:43 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Ingo Molnar <mingo@...nel.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
        "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Artem Bityutskiy <dedekind1@...il.com>,
        linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
        Richard Weinberger <richard@....at>
Subject: Re: linux-next: build warning after merge of the tip tree

Hi Ingo,

On Wed, 14 Dec 2016 08:24:11 +0100 Ingo Molnar <mingo@...nel.org> wrote:
>
> FYI, f4f61d2cc6d8 is not in the -tip tree, so it cannot possibly have introduced 
> this warning.

Yeah, I know, but the warning only seemed to happen after merging the
tip tree.  I would have expected it to appear much earlier like when I
merged the ubifs tree.  I figured that out, but forgot to mention it,
sorry.

Actually I just checked and it did turn up then, but my heuristics did
not point it out :-(
-- 
Cheers,
Stephen Rothwell