linux-kernel - Re: Preempt-RT patch for 2.6.25

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:	Mon, 05 May 2008 09:17:30 -0700
From:	Daniel Walker <dwalker@...sta.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Sven-Thorsten Dietrich <sven@...bigcorporation.com>,
	Remy Bohmer <linux@...mer.net>,
	LKML <linux-kernel@...r.kernel.org>,
	RT <linux-rt-users@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Jon Masters <jonathan@...masters.org>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: Preempt-RT patch for 2.6.25


On Fri, 2008-05-02 at 14:45 -0400, Steven Rostedt wrote:
> On Fri, 2 May 2008, Sven-Thorsten Dietrich wrote:
> >
> >
> > His bi-sectability changes are pretty key, and I would like to see those
> > reviewed and incorporated, even if they apply only to x86.
> 
> They would be nice, but I'm also in the process of moving patches around
> to have the next mainline enhancement up front.

Not sure what that has to do with bisect changes?

> >
> > The RT patch queue generally is a mess today.
> > Lots of stuff needs to be folded down into the core patches.
> 
> I'm starting to fold patches together too.

You really want bisection first. The reason is that you don't want ever
growing patches, you want smaller and smaller patches. For instance the
rt-mutex-core.patch is way too large, you wouldn't want to fold my
PICK_FUNCTION changes into that patch since that would just make
rt-mutex-core larger ..


Daniel

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