linux-kernel - Re: [000/474] 2.6.33.8-longterm review

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:	Sun, 20 Mar 2011 13:52:50 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Remy Bohmer <linux@...mer.net>
cc:	Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [000/474] 2.6.33.8-longterm review

On Sat, 19 Mar 2011, Remy Bohmer wrote:

> Hi,
> 
> 2011/3/18 Thomas Gleixner <tglx@...utronix.de>:
> > On Thu, 17 Mar 2011, Greg KH wrote:
> >
> >> Yeah, I know what you are thinking, "What, 2.6.33, are you crazy?"
> >
> > Aren't we all crazy ?
> >
> >> I'd prefer it if you didn't answer that question...
> >
> > Too late. You should have put this before the question.
> >
> >> So, if you are using .33, please give this patch a test and let me know
> >> if I've messed up anything (hint, I think I did, it's up to you to
> >> figure it out, consider it a test to see if anyone actually cares about
> >> this kernel version.)
> >
> > We'll pull it into rt and figure out what breaks.
> 
> Can you please elaborate somewhat on the status of the RT-patchset
> development for 2.6.38 and on?

Working on it.

> It is silent about it for quite a while now, and actually the gap
> between mainstream and the latest RT has never been this big before...
> Are there major complications, lack on time or hands? Can I help ?

I concentrated on getting stuff upstream and reworking to make it more
palatable and maintainable.

Thanks,

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