From: Jingoo Han <jg1.han@samsung.com>
To: Venu Byravarasu <vbyravarasu@nvidia.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"'Alessandro Zummo'" <a.zummo@towertech.it>,
"rtc-linux@googlegroups.com" <rtc-linux@googlegroups.com>,
Jingoo Han <jg1.han@samsung.com>
Subject: Re: [PATCH 03/11] rtc: rtc-efi: use pr_err()/pr_warn() instead of printk()
Date: Fri, 15 Feb 2013 06:37:49 +0000 (GMT) [thread overview]
Message-ID: <5139267.654181360910268438.JavaMail.weblogic@epml24> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=euc-kr, Size: 2142 bytes --]
On Friday, February 15, 2013 3:04 PM, Venu Byravarasu wrote:
>
> > -----Original Message-----
> > From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-
> > owner@vger.kernel.org] On Behalf Of Jingoo Han
> > Sent: Friday, February 15, 2013 11:29 AM
> > To: 'Andrew Morton'
> > Cc: linux-kernel@vger.kernel.org; 'Alessandro Zummo'; rtc-
> > linux@googlegroups.com; 'Jingoo Han'
> > Subject: [PATCH 03/11] rtc: rtc-efi: use pr_err()/pr_warn() instead of printk()
> >
> > Fixed the checkpatch warnings as below:
> >
> > WARNING: Prefer netdev_err(netdev, ... then dev_err(dev, ... then pr_err(...
> > to printk(KERN_ERR ...
> > WARNING: please, no space before tabs
> >
> > Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> > ---
> > drivers/rtc/rtc-efi.c | 10 ++++++----
> > 1 files changed, 6 insertions(+), 4 deletions(-)
> >
> > eft->timezone = EFI_UNSPECIFIED_TIMEZONE;
> > @@ -142,7 +144,7 @@ static int efi_set_alarm(struct device *dev, struct
> > rtc_wkalrm *wkalrm)
> > */
> > status = efi.set_wakeup_time((efi_bool_t)wkalrm->enabled, &eft);
> >
> > - printk(KERN_WARNING "write status is %d\n", (int)status);
> > + pr_warn("write status is %d\n", (int)status);
>
> Why don't you use dev_warn itself?
OK, I will change it.
Thank you.
Best regards,
Jingoo Han
>
> >
> > return status == EFI_SUCCESS ? 0 : -EINVAL;
> > }
> > @@ -157,7 +159,7 @@ static int efi_read_time(struct device *dev, struct
> > rtc_time *tm)
> >
> > if (status != EFI_SUCCESS) {
> > /* should never happen */
> > - printk(KERN_ERR "efitime: can't read time\n");
> > + pr_err("can't read time\n");
>
> Why don't you use dev_err itself?
>
> > return -EINVAL;
> > }
> >
> > --
> > 1.7.2.5
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next reply other threads:[~2013-02-15 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 6:37 Jingoo Han [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-02-15 5:57 [PATCH 01/11] rtc: use pr_err()/pr_warn() instead of printk() Jingoo Han
2013-02-15 5:58 ` [PATCH 03/11] rtc: rtc-efi: " Jingoo Han
2013-02-15 6:04 ` Venu Byravarasu
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=5139267.654181360910268438.JavaMail.weblogic@epml24 \
--to=jg1.han@samsung.com \
--cc=a.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rtc-linux@googlegroups.com \
--cc=vbyravarasu@nvidia.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).