From: akpm@linux-foundation.org
To: w.sang@pengutronix.de, a.v.rooyen@sercom.nl,
a.zummo@towertech.it, stable@kernel.org,
mm-commits@vger.kernel.org
Subject: [merged] rtc-rs5c372-fix-buffer-size.patch removed from -mm tree
Date: Thu, 23 Dec 2010 14:36:36 -0800 [thread overview]
Message-ID: <201012232240.oBNMeOSD015449@imap1.linux-foundation.org> (raw)
The patch titled
rtc: rs5c372: fix buffer size
has been removed from the -mm tree. Its filename was
rtc-rs5c372-fix-buffer-size.patch
This patch was dropped because it was merged into mainline or a subsystem tree
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: rtc: rs5c372: fix buffer size
From: Wolfram Sang <w.sang@pengutronix.de>
Match the buffer size to the amount of initialized values. Before, it was
one too big and thus destroyed the neighbouring register causing the clock
to run at false speeds.
Reported-by: Andre van Rooyen <a.v.rooyen@sercom.nl>
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Cc: Alessandro Zummo <a.zummo@towertech.it>
Cc: <stable@kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
drivers/rtc/rtc-rs5c372.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/rtc/rtc-rs5c372.c~rtc-rs5c372-fix-buffer-size drivers/rtc/rtc-rs5c372.c
--- a/drivers/rtc/rtc-rs5c372.c~rtc-rs5c372-fix-buffer-size
+++ a/drivers/rtc/rtc-rs5c372.c
@@ -207,7 +207,7 @@ static int rs5c372_get_datetime(struct i
static int rs5c372_set_datetime(struct i2c_client *client, struct rtc_time *tm)
{
struct rs5c372 *rs5c = i2c_get_clientdata(client);
- unsigned char buf[8];
+ unsigned char buf[7];
int addr;
dev_dbg(&client->dev, "%s: tm is secs=%d, mins=%d, hours=%d "
_
Patches currently in -mm which might be from w.sang@pengutronix.de are
origin.patch
linux-next.patch
pata_mpc52xx-driver-needs-bmdma.patch
reply other threads:[~2010-12-23 22:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201012232240.oBNMeOSD015449@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=a.v.rooyen@sercom.nl \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=stable@kernel.org \
--cc=w.sang@pengutronix.de \
/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.