All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eduardo Valentin <edubezval@gmail.com>
To: Caesar Wang <caesar.upstream@gmail.com>
Cc: Zhang Rui <rui.zhang@intel.com>, Caesar Wang <wxt@rock-chips.com>,
	Heiko Stuebner <heiko@sntech.de>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Laxman Dewangan <ldewangan@nvidia.com>,
	smbarber@google.com, Durgadoss R <durgadoss.r@intel.com>,
	Jonathan Corbet <corbet@lwn.net>,
	linux-rockchip@lists.infradead.org, briannorris@google.com,
	Andy Champ <andycham@amazon.com>,
	huangtao@rock-chips.com, linux-pm@vger.kernel.org,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Javi Merino <javi.merino@arm.com>,
	linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	Ni Wade <wni@nvidia.com>, Keerthy <j-keerthy@ti.com>,
	dmitry.torokhov@gmail.com, dianders@chromium.org,
	Leo Yan <leo.yan@linaro.org>,
	cf@rock-chips.com
Subject: Re: [PATCH v2 0/5] Thermal: Support for hardware-tracked trip points
Date: Mon, 23 May 2016 20:08:27 -0700	[thread overview]
Message-ID: <20160524030825.GA3489@localhost.localdomain> (raw)
In-Reply-To: <5742B217.4080405@gmail.com>

On Mon, May 23, 2016 at 03:32:39PM +0800, Caesar Wang wrote:
> Hello Eduardo & 'Zhang Rui'
> 
> Do we have the chance to merge this series patches for next kernel?
> I had picked them up in my github, and tested for a period of time with
> rockchip inside kernel.
> 
> Let me know if someone have some suggestions or against opinios.
> Thanks,

I will have a look after after the current merge window.

Thanks.


WARNING: multiple messages have this Message-ID (diff)
From: edubezval@gmail.com (Eduardo Valentin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] Thermal: Support for hardware-tracked trip points
Date: Mon, 23 May 2016 20:08:27 -0700	[thread overview]
Message-ID: <20160524030825.GA3489@localhost.localdomain> (raw)
In-Reply-To: <5742B217.4080405@gmail.com>

On Mon, May 23, 2016 at 03:32:39PM +0800, Caesar Wang wrote:
> Hello Eduardo & 'Zhang Rui'
> 
> Do we have the chance to merge this series patches for next kernel?
> I had picked them up in my github, and tested for a period of time with
> rockchip inside kernel.
> 
> Let me know if someone have some suggestions or against opinios.
> Thanks,

I will have a look after after the current merge window.

Thanks.

  reply	other threads:[~2016-05-24  3:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-03  9:33 [PATCH v2 0/5] Thermal: Support for hardware-tracked trip points Caesar Wang
2016-05-03  9:33 ` Caesar Wang
     [not found] ` <1462268013-14992-1-git-send-email-wxt-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2016-05-03  9:33   ` [PATCH v2 1/5] thermal: Add support " Caesar Wang
2016-05-03  9:33     ` Caesar Wang
2016-05-24 12:57     ` Javi Merino
2016-05-25  3:27       ` Caesar Wang
2016-05-25 16:44         ` Javi Merino
2016-05-03  9:33 ` [PATCH v2 2/5] thermal: of: implement .set_trips for device tree thermal zones Caesar Wang
2016-05-24 13:01   ` Javi Merino
2016-05-25  3:28     ` Caesar Wang
2016-05-03  9:33 ` [PATCH v2 3/5] thermal: streamline get_trend callbacks Caesar Wang
2016-05-03  9:33 ` [PATCH v2 4/5] thermal: bang-bang governor: act on lower trip boundary Caesar Wang
2016-05-24 13:06   ` Javi Merino
2016-05-24 13:11     ` Peter Feuerer
2016-05-24 17:34     ` Peter Feuerer
     [not found]       ` <a942e788aa285dcf88db38c6d03a36ce-wZNyVc2rXxoqcZcGjlUOXw@public.gmane.org>
2016-05-25  3:30         ` Caesar Wang
2016-05-25  3:30           ` Caesar Wang
2016-05-03  9:33 ` [PATCH v2 5/5] thermal: rockchip: add the set_trips function Caesar Wang
2016-05-03  9:33   ` Caesar Wang
2016-05-23  7:32 ` [PATCH v2 0/5] Thermal: Support for hardware-tracked trip points Caesar Wang
2016-05-23  7:32   ` Caesar Wang
2016-05-24  3:08   ` Eduardo Valentin [this message]
2016-05-24  3:08     ` Eduardo Valentin

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=20160524030825.GA3489@localhost.localdomain \
    --to=edubezval@gmail.com \
    --cc=andycham@amazon.com \
    --cc=briannorris@google.com \
    --cc=caesar.upstream@gmail.com \
    --cc=cf@rock-chips.com \
    --cc=corbet@lwn.net \
    --cc=dianders@chromium.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=durgadoss.r@intel.com \
    --cc=heiko@sntech.de \
    --cc=huangtao@rock-chips.com \
    --cc=j-keerthy@ti.com \
    --cc=javi.merino@arm.com \
    --cc=ldewangan@nvidia.com \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=rui.zhang@intel.com \
    --cc=s.hauer@pengutronix.de \
    --cc=smbarber@google.com \
    --cc=wni@nvidia.com \
    --cc=wxt@rock-chips.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.