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]
Date:	Tue, 2 Oct 2007 12:48:05 +0200
From:	Andi Kleen <ak@...e.de>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, Greg KH <greg@...ah.com>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	akpm@...l.org
Subject: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..

On Tuesday 02 October 2007 12:37:55 Jeff Garzik wrote:
> Andi Kleen wrote:
> > On Tuesday 02 October 2007 11:17:02 Thomas Gleixner wrote:
> >>> This is also a good time to warn about the fact that we're doing the x86 
> >>> merge very soon (as in the next day or two) after 2.6.23 is out, so if you 
> >>> have pending patches for the next series that touch arch/i386 or x86-64, 
> >>> you should get in touch with Thomas Gleixner and Ingo Molnar, who are the 
> >>> keepers of the merge scripts, and will help you prepare..
> > 
> > 
> > Yes I have ~100 patches for arch/x86_64, arch/i386
> > 
> > Should I just drop them?
> 
> Why don't you work with Thomas and Ingo to make sure everything is in 
> sync and prepped for 2.6.24?

The easiest way to do that would be to first merge all the queued and
collected patches from the last months. Once they are in people
can then create whatever mess they like.

The other way round  (adapting 100+ patches to a possibly completely
different tree) will be a huge amount of work which I am
frankly not very motivated to do because I think it's quite unnecessary. 

I would probably just push the work back to all the patch submitters -- that is 
what I meant with dropping the patches.

I assume mess up first would be also a minor catastrophe for Andrew --
in addition to my patches he also has a large number of patches
touching {x86_64,i386}

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ