linux-kernel - Re: [PATCH v5 0/5] x86: Cleanup and simplify cpu-specific data

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: <CAELBVzAN33S4_VATnO7FaNjNaObqHsp+OXPsQYeve1N_qUztcA@mail.gmail.com>
Date:	Fri, 27 Apr 2012 20:37:36 -0300
From:	Kevin Winchester <kjwinchester@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Nick Bowler <nbowler@...iptictech.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Randy Dunlap <rdunlap@...otime.net>,
	Borislav Petkov <bp@...en8.de>
Subject: Re: [PATCH v5 0/5] x86: Cleanup and simplify cpu-specific data

On 26 April 2012 18:21, H. Peter Anvin <hpa@...or.com> wrote:
> Against mainline would be better, unless it actively conflicts with something in tip.
>

Alright, my git/make skills must be lacking.  I just checked out
3.4-rc4 to a new branch, and then git cherry-picked my 5 patches onto
that branch.  Then I ran:

$ make ARCH=i386 allnoconfig
$ make ARCH=i386

And the build completed without warnings or errors.  Should that be
equivalent to what you did to build i386 allnoconfig?  If so, then I
wonder why I would not see those problems.

Can anyone offer any advice?

Thanks,

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