linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: linux-next <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Amit Kachhap <amit.kachhap@linaro.org>,
	guenter.roeck@ericsson.com, kuninori.morimoto.gx@renesas.com,
	akpm@linux-foundation.org
Subject: thermal patches in linux-next
Date: Tue, 07 Aug 2012 10:53:58 +0800	[thread overview]
Message-ID: <1344308038.1682.637.camel@rui.sh.intel.com> (raw)

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

             reply	other threads:[~2012-08-07  2:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  2:53 Zhang Rui [this message]
2012-08-07  4:40 ` thermal patches in linux-next Kuninori Morimoto
2012-08-07 12:13 ` Amit Kachhap
     [not found] ` <1344494746.1682.669.camel@rui.sh.intel.com>
2012-08-09 23:08   ` Stephen Rothwell
2012-08-10  1:41     ` Zhang Rui
2012-08-10  2:23       ` Stephen Rothwell
2012-08-10  2:44         ` Zhang Rui
2012-08-10  5:07           ` Amit Kachhap
2012-08-10  5:51             ` Zhang Rui
2012-08-14  6:15               ` Amit Kachhap
     [not found]                 ` <CAK44p23u18MsDxPL_NkZqJLpstJJAGTfxDP4SCSuFuYzQq8-oA@mail.gmail.com>
2012-08-17  0:42                   ` Zhang Rui

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1344308038.1682.637.camel@rui.sh.intel.com \
    --to=rui.zhang@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=amit.kachhap@linaro.org \
    --cc=guenter.roeck@ericsson.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).