From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Guan Xuetao <gxt@mprc.pku.edu.cn>,
a.zummo@towertech.it, sangjung.woo@samsung.com
Cc: rtc-linux@googlegroups.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 2/2] drivers/rtc/rtc-puv3.c: remove "&dev->" for typo issue MIME-Version: 1.0
Date: Sat, 03 May 2014 13:09:02 +0800 [thread overview]
Message-ID: <536479EE.4090500@gmail.com> (raw)
In-Reply-To: <53647962.6070006@gmail.com>
It is only a typo issue, the related commit:
"1fbc4c4 drivers/rtc/rtc-puv3.c: use dev_dbg() instead of pr_debug()"
The related error (for unicore32 with allmodconfig):
CC [M] drivers/rtc/rtc-puv3.o
drivers/rtc/rtc-puv3.c: In function ‘puv3_rtc_setalarm’:
drivers/rtc/rtc-puv3.c:143: error: ‘struct device’ has no member named ‘dev’
Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
---
drivers/rtc/rtc-puv3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-puv3.c b/drivers/rtc/rtc-puv3.c
index c56310e..1cff2a2 100644
--- a/drivers/rtc/rtc-puv3.c
+++ b/drivers/rtc/rtc-puv3.c
@@ -140,7 +140,7 @@ static int puv3_rtc_setalarm(struct device *dev, struct rtc_wkalrm *alrm)
rtc_tm_to_time(tm, &rtcalarm_count);
writel(rtcalarm_count, RTC_RTAR);
- puv3_rtc_setaie(&dev->dev, alrm->enabled);
+ puv3_rtc_setaie(dev, alrm->enabled);
if (alrm->enabled)
enable_irq_wake(puv3_rtc_alarmno);
--
1.9.2.459.g68773ac
next prev parent reply other threads:[~2014-05-03 5:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-03 5:06 [PATCH 0/2] drivers/rtc/rtc-puv3.c: fix 2 typo issues Chen Gang
2014-05-03 5:07 ` [PATCH 1/2] drivers/rtc/rtc-puv3.c: use dev_dbg() instead of dev_debug() for typo issue Chen Gang
2014-05-12 7:53 ` 回复： " 管雪涛
2014-05-03 5:09 ` Chen Gang [this message]
2014-05-12 7:56 ` 回复： [PATCH 2/2] drivers/rtc/rtc-puv3.c: remove "&dev->" for typo issue MIME-Version: 1.0 管雪涛
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=536479EE.4090500@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=a.zummo@towertech.it \
--cc=gxt@mprc.pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=sangjung.woo@samsung.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).