linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhang Rui <rui.zhang@intel.com>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Simon <horms@verge.net.au>, Magnus <magnus.damm@gmail.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>,
	linux-pm@vger.kernel.org, Linux-SH <linux-sh@vger.kernel.org>
Subject: Re: [PATCH 0/2 v2] thermal: rcar: fixup registration failure case
Date: Tue, 26 Mar 2013 14:30:55 +0800	[thread overview]
Message-ID: <1364279455.2821.2.camel@rzhang1-mobl4> (raw)
In-Reply-To: <87r4j2itio.wl%kuninori.morimoto.gx@renesas.com>

On Mon, 2013-03-25 at 23:07 -0700, Kuninori Morimoto wrote:
> Hi Zhang
> 
> These are v2 patch set of rcar_thermal driver fixup
> I noticed that v1 patch had bug.
> 
it seems that you did not run any test for the previous patch set, not
even build test.

have you tried this patch set before sending out?

thanks,
rui
> These patch set are for linus/master branch,
> and, these requires zhang/next's
> 
> f0e68fc3caf677e834f7bd0f601800e686b56c98
> (thermal: rcar: fix missing unlock on error in rcar_thermal_update_temp())
> 
> fb84d9907f0ff0e3f7d70d55039ddf0f78d2a472
> (thermal: rcar_thermal: propagate return value of thermal_zone_device_register)
> 
> current linus/master branch needs above 2 patches,
> and these patch set are based on these.
> 
> I Cc:ed SH-ARM ML
> 
> Kuninori Morimoto (2):
>       thermal: rcar: tidyup registration failure case
>       thermal: rcar: add pm_runtime_xxx() support
> 
>  drivers/thermal/rcar_thermal.c |   31 +++++++++++++++++++++++++------
>  1 file changed, 25 insertions(+), 6 deletions(-)
> 
> Best regards
> ---
> Kuninori Morimoto
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



  parent reply	other threads:[~2013-03-26  6:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-25  5:48 [PATCH 0/2] thermal: rcar: fixup registration failure case Kuninori Morimoto
2013-03-25  5:49 ` [PATCH 1/2] thermal: rcar: tidyup " Kuninori Morimoto, Kuninori Morimoto
2013-03-25  8:40   ` Zhang Rui
2013-03-26  0:16     ` Kuninori Morimoto
2013-03-26  5:53       ` Kuninori Morimoto
2013-03-26  6:07         ` [PATCH 0/2 v2] thermal: rcar: fixup " Kuninori Morimoto
2013-03-26  6:08           ` [PATCH 1/2 v2] thermal: rcar: tidyup " Kuninori Morimoto
2013-04-02 13:17             ` Zhang Rui
2013-03-26  6:08           ` [PATCH 2/2 v2] thermal: rcar: add pm_runtime_xxx() support Kuninori Morimoto
2013-04-02 13:19             ` Zhang Rui
2013-03-26  6:30           ` Zhang Rui [this message]
2013-03-26  6:45             ` [PATCH 0/2 v2] thermal: rcar: fixup registration failure case Kuninori Morimoto
2013-03-25  5:50 ` [PATCH 2/2] thermal: rcar: add pm_runtime_xxx() support Kuninori Morimoto, Kuninori Morimoto

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=1364279455.2821.2.camel@rzhang1-mobl4 \
    --to=rui.zhang@intel.com \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@gmail.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.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).