linux-kernel - Re: [GIT PULL] percpu fixes for 2.6.31-rc8

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: <4A9D1A18.5000201@kernel.org>
Date:	Tue, 01 Sep 2009 21:56:56 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Linux Kernel <linux-kernel@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Meelis Roos <mroos@...ux.ee>
Subject: Re: [GIT PULL] percpu fixes for 2.6.31-rc8

Tejun Heo wrote:
> Hello, Linus.
> 
> Please consider pulling from the following percpu fixes tree.
> 
>  git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu.git for-linus

Ummm... one question.  The above tree is on top of the previous
for-linus fixes tree.  It pulls in to the current #master alright but
it would still be a merge instead of a fast-forward.  Would it be
better to prep fixes tree on top of the current #master so that it
results in fast-forward?  If that's the case, please let me know or
just cherry pick the top commit.

Thanks.

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