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] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 3 Dec 2012 00:59:07 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Request for tree inclusion

2012/12/2 Stephen Rothwell <sfr@...b.auug.org.au>:
> Well, these are a bit late (I expected Linus to release v3.7 today), but
> since Ingo has not piped in over the weekend, I have added them from today
> after the tip tree merge.

Yeah sorry to submit that so late. Those branches are in pending pull
requests to the -tip tree and I thought about relying on the
propagation of -tip into -next as usual. But Ingo has been very busy
with numa related work during this cycle. So until these branches get
merged in -tip, I'm short-circuiting a bit the -next step before it
becomes too late for the next merge window.

>
> I have called them fw-cputime, fs-sched and fw-nohz respectively and
> listed you as the only contact in case of problems.

Ok.

> If these are to be
> long term trees included in linux-next, I would prefer that you use
> better branch names - otherwise, if they are just short term, please tell
> me to remove them when they are finished with.

They are definitely short term. I'll tell you once these can be dropped.

Thanks a lot!
--
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/