linux-kernel - Re: [RFC PATCH 0/3] Series short description

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]

Message-ID: <20081203204025.GA31376@elte.hu>
Date:	Wed, 3 Dec 2008 21:40:25 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Gregory Haskins <gregory.haskins.ml@...il.com>
Cc:	Gregory Haskins <ghaskins@...ell.com>, rostedt@...dmis.org,
	peterz@...radead.org, linux-kernel@...r.kernel.org,
	=linux-rt-users@...r.kernel.org
Subject: Re: [RFC PATCH 0/3] Series short description


* Gregory Haskins <gregory.haskins.ml@...il.com> wrote:

> Gregory Haskins wrote:
> > Hi Ingo, Steven, Peter,
> >   This series applies roughly to mainline as an enhancement to the sched_rt
> >   logic.  Peter and I were discussing some of the unecessary overhead in
> >   pull_rt_tasks() via IRC, and this is my RFC attempt to address the problem.
> >   
> 
> Hi Ingo,
>   I was putting together a refresh of this patch and I rebased on
> tip/sched/devel.  I noticed that sched/devel is on 27-rc8, which is
> obviously a little stale.  Is this the proper tree to send patches
> against, or would you prefer a different HEAD?

tip/master would be the base to use, or tip/sched/core. The sched/devel 
branch is indeed stale.

	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/