linux-kernel - Re: Request for tree inclusion

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: <20130112121536.c7c9371672bcf3afc5c2925d@canb.auug.org.au>
Date:	Sat, 12 Jan 2013 12:15:36 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	linux-next@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Request for tree inclusion

Hi Frederic,

On Fri, 11 Jan 2013 02:15:39 +0100 Frederic Weisbecker <fweisbec@...il.com> wrote:
>
> fw-cputime and fs-sched have been merged so you can now remove these
> branches from next.

Done.

> But fw-nohz remains. In the meantime I have created a branch named nohz/next:
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/frederic/linux-dynticks.git
>         nohz/next
> 
> This branch currently refers to fw-nohz HEAD (aka nohz/printk-v8) and
> this is also the place where I'll gather -next materials in the future
> instead of the multiple branches you're currently pulling.
> So could you please remove fw-nohz (nohz/printk-v8) as well from -next
> but include nohz/next instead?

Also done.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped