From 4f673254a82719c40ed06af804df80e8c113e211 Mon Sep 17 00:00:00 2001
From: Paul Mundt <lethal@linux-sh.org>
Date: Mon, 28 Apr 2008 02:11:57 -0700
Subject: [PATCH] --- yaml --- r: 93967 b: refs/heads/master c:
 e2bfe3424b368e977002fc58f81536d5d8ea9449 h: refs/heads/master i:   93965:
 df977c00dafebc2a1775b34407875f78e8578dbd   93963:
 626d796e22ba6bb4ea50126f4fbe68313205a085   93959:
 256a25b19e48337da95d36dbcc26b2317e49cc06   93951:
 3d9b405d9b2ce5763867608ebcee5ab3f826f2f6 v: v3

---
 [refs]                          | 2 +-
 trunk/drivers/rtc/rtc-rs5c372.c | 8 ++++----
 2 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/[refs] b/[refs]
index 9bcc7b0bab88..8c58d91826fd 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: e275ac477161a3df5c27e40c55f7af94cfb396cf
+refs/heads/master: e2bfe3424b368e977002fc58f81536d5d8ea9449
diff --git a/trunk/drivers/rtc/rtc-rs5c372.c b/trunk/drivers/rtc/rtc-rs5c372.c
index 6b67b5097927..67d8768c1b64 100644
--- a/trunk/drivers/rtc/rtc-rs5c372.c
+++ b/trunk/drivers/rtc/rtc-rs5c372.c
@@ -99,7 +99,7 @@ static int rs5c_get_regs(struct rs5c372 *rs5c)
 	 * least 80219 chips; this works around that bug.
 	 */
 	if ((i2c_transfer(client->adapter, msgs, 1)) != 1) {
-		pr_debug("%s: can't read registers\n", rs5c->rtc->name);
+		dev_warn(&client->dev, "can't read registers\n");
 		return -EIO;
 	}
 
@@ -512,12 +512,12 @@ static int rs5c372_probe(struct i2c_client *client)
 		goto exit;
 	}
 
-	/* we read registers 0x0f then 0x00-0x0f; skip the first one */
-	rs5c372->regs=&rs5c372->buf[1];
-
 	rs5c372->client = client;
 	i2c_set_clientdata(client, rs5c372);
 
+	/* we read registers 0x0f then 0x00-0x0f; skip the first one */
+	rs5c372->regs = &rs5c372->buf[1];
+
 	err = rs5c_get_regs(rs5c372);
 	if (err < 0)
 		goto exit_kfree;