linux-kernel - thermal patches in linux-next

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

Date:	Tue, 07 Aug 2012 10:53:58 +0800
From:	Zhang Rui <rui.zhang@...el.com>
To:	linux-next <linux-next@...r.kernel.org>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Amit Kachhap <amit.kachhap@...aro.org>,
	guenter.roeck@...csson.com, kuninori.morimoto.gx@...esas.com,
	akpm@...ux-foundation.org
Subject: thermal patches in linux-next

Hi, all,

I just created a git tree for catching all thermal changes.
http://git.kernel.org/?p=linux/kernel/git/rzhang/linux.git;a=summary
and I also created the next branch, which I'd like to be set for
linux-next inclusion, but don't know how.

And, I just saw that there are a couple of thermal patches in
linux-next, which I think it would be better if they can be re-based on
my next branch first.
For Guenter's and Kuninori's patch, I can take them directly, with few
changes.

Amit,
I really like the idea of generic cpufreq cooling. But can you please
rebase the patches on top of my next branch? the recent thermal changes
will make your patch much cleaner, as we discussed before. :)

thanks,
rui

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