linux-kernel - Re: Why not creating a GIT RT tree ?

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]

Message-ID: <20080121074524.GA20072@linux-sh.org>
Date:	Mon, 21 Jan 2008 16:45:24 +0900
From:	Paul Mundt <lethal@...ux-sh.org>
To:	Francis Moreau <francis.moro@...il.com>
Cc:	Steven Rostedt <rostedt@...dmis.org>, matsu@...l.co.jp,
	linux-kernel@...r.kernel.org
Subject: Re: Why not creating a GIT RT tree ?

On Sat, Jan 19, 2008 at 08:41:18PM +0100, Francis Moreau wrote:
> On Jan 18, 2008 8:12 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> > True, but then how would you do it. One thing is that most of these
> > branches would interact with each other. Touching the same code quite
> > a bit. So it doesn't always help. But pulling out patches can help us to
> > an extent.
> >
> 
> I see, it would probably be too painful in this context, that's pity.
> 
> >
> > Great! Looking forward to it ;-)
> >
> 
> Well actually it seems already supported. Some files in arch/sh
> are already touched by RT patches.
> 
At least it sees fairly regular testing on SH7751R and SH7780, you may
wish to discuss this with Matsubara-san (added to CC) though, as he does
most of the work in this area. I don't get much time to look at it.
--
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/