linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Zhang Rui <rui.zhang@intel.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Devendra Naga <develkernel412222@gmail.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Durgadoss R <durgadoss.r@intel.com>
Subject: linux-next: manual merge of the thermal tree with Linus' tree
Date: Mon, 5 Nov 2012 11:46:44 +1100	[thread overview]
Message-ID: <20121105114644.fe54cba816860bf12f1de9cf@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

Hi Zhang,

Today's linux-next merge of the thermal tree got a conflict in
drivers/thermal/rcar_thermal.c between commit 608f62b996c6 ("thermal:
solve compilation errors in rcar_thermal") from Linus' tree and commit
ebbf0f11e7b4 ("Thermal: Pass zone parameters as argument to
tzd_register") from the thermal tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc drivers/thermal/rcar_thermal.c
index f7a1b57,b13fe5d..0000000
--- a/drivers/thermal/rcar_thermal.c
+++ b/drivers/thermal/rcar_thermal.c
@@@ -210,8 -210,8 +210,8 @@@ static int rcar_thermal_probe(struct pl
  		goto error_free_priv;
  	}
  
 -	zone = thermal_zone_device_register("rcar_thermal", 0, priv,
 +	zone = thermal_zone_device_register("rcar_thermal", 0, 0, priv,
- 					    &rcar_thermal_zone_ops, 0, 0);
+ 				    &rcar_thermal_zone_ops, NULL, 0, 0);
  	if (IS_ERR(zone)) {
  		dev_err(&pdev->dev, "thermal zone device is NULL\n");
  		ret = PTR_ERR(zone);

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2012-11-05  0:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-05  0:46 Stephen Rothwell [this message]
2012-11-05  1:17 ` linux-next: manual merge of the thermal tree with Linus' tree Zhang Rui
2012-11-05  6:47 ` Zhang Rui
2019-09-20 12:46 Mark Brown
2021-09-26 23:50 Stephen Rothwell
2022-08-14 23:20 Stephen Rothwell

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=20121105114644.fe54cba816860bf12f1de9cf@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=develkernel412222@gmail.com \
    --cc=durgadoss.r@intel.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).