linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amit Kachhap <amit.kachhap@linaro.org>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-next <linux-next@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	guenter.roeck@ericsson.com, kuninori.morimoto.gx@renesas.com,
	akpm@linux-foundation.org
Subject: Re: thermal patches in linux-next
Date: Tue, 7 Aug 2012 17:43:30 +0530	[thread overview]
Message-ID: <CAK44p22ewPR2h_KLqHjmNY4KVG-E68s5BxdUXrzRy_hk4Nf7Cg@mail.gmail.com> (raw)
In-Reply-To: <1344308038.1682.637.camel@rui.sh.intel.com>

Hi,

Thanks Rui for creating the next tree. I will rebase my patches on top
of your tree and post them shortly.

Thanks,
Amit Daniel

On 7 August 2012 08:23, Zhang Rui <rui.zhang@intel.com> wrote:
> 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
>

  parent reply	other threads:[~2012-08-07 12:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07  2:53 thermal patches in linux-next Zhang Rui
2012-08-07  4:40 ` Kuninori Morimoto
2012-08-07 12:13 ` Amit Kachhap [this message]
     [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=CAK44p22ewPR2h_KLqHjmNY4KVG-E68s5BxdUXrzRy_hk4Nf7Cg@mail.gmail.com \
    --to=amit.kachhap@linaro.org \
    --cc=akpm@linux-foundation.org \
    --cc=guenter.roeck@ericsson.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    /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).