The patch titled
Subject: rtc: hctosys: use function name in the error log
has been added to the -mm tree. Its filename is
rtc-hctosys-use-function-name-in-the-error-log.patch
This patch should soon appear at
http://ozlabs.org/~akpm/mmots/broken-out/rtc-hctosys-use-function-name-in-the-error-log.patch
and later at
http://ozlabs.org/~akpm/mmotm/broken-out/rtc-hctosys-use-function-name-in-the-error-log.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Aaro Koskinen <aaro.koskinen@xxxxxx>
Subject: rtc: hctosys: use function name in the error log
Use function name in the error log instead of __FILE__.
Signed-off-by: Aaro Koskinen <aaro.koskinen@xxxxxx>
Cc: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxxxxxxxxx>
Cc: Alessandro Zummo <a.zummo@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/rtc/hctosys.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN drivers/rtc/hctosys.c~rtc-hctosys-use-function-name-in-the-error-log drivers/rtc/hctosys.c
--- a/drivers/rtc/hctosys.c~rtc-hctosys-use-function-name-in-the-error-log
+++ a/drivers/rtc/hctosys.c
@@ -33,7 +33,7 @@ static int __init rtc_hctosys(void)
if (rtc == NULL) {
pr_info("%s: unable to open rtc device (%s)\n",
- __FILE__, CONFIG_RTC_HCTOSYS_DEVICE);
+ __func__, CONFIG_RTC_HCTOSYS_DEVICE);
goto err_open;
}
_
Patches currently in -mm which might be from aaro.koskinen@xxxxxx are
rtc-initialize-rtc-name-early.patch
rtc-__rtc_read_time-reduce-log-level.patch
rtc-hctosys-use-function-name-in-the-error-log.patch
linux-next.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
