linux-kernel - Re: [git-pull -tip] x86: mpparse cleanup

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

Date:	Fri, 20 Mar 2009 19:43:11 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
Cc:	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git-pull -tip] x86: mpparse cleanup


* Jaswinder Singh Rajput <jaswinder@...nel.org> wrote:

> On Wed, 2009-03-18 at 17:18 +0100, Ingo Molnar wrote:
> 
> > Looks good - pulled, thanks Jaswinder!
> > 
> > Would you be interested in resurrecting the more mechanic cleanups 
> > you did as well, on top of this patch?
> > 
> > They are still valuable, we just have to keep them separate from a 
> > potential breakage-causing change like the above one, so that if a 
> > tester bisects to it, we have an as single-purpose and focused 
> > commit to look at as possible.
> > 
> 
> cleanup without code change: based on tip:x86/core or x86/cleanups
> or .. ?
> 
> cleanup with code change: based on tip:x86/core or x86/cleanups or .. ?

Any of the x86/* branches is fine - they are permanent branches. 
(tip:master gets reintegrated every week or so)

x86/core would be the best choice.

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