All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Heitke <kheitke@codeaurora.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Anirudh Ghayal <aghayal@codeaurora.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	rtc-linux@googlegroups.com, Wan ZongShun <mcuos.com@gmail.com>,
	linux-arm-msm@vger.kernel.org,
	Ashay Jaiswal <ashayj@codeaurora.org>
Subject: Re: [PATCH V3] drivers: rtc: Add support for Qualcomm PMIC8xxx RTC
Date: Thu, 26 May 2011 16:22:24 -0600	[thread overview]
Message-ID: <4DDED2A0.2070109@codeaurora.org> (raw)
In-Reply-To: <4DDE8FC8.3020405@codeaurora.org>

On 05/26/2011 11:37 AM, Stephen Boyd wrote:
> On 5/25/2011 10:15 PM, Anirudh Ghayal wrote:
>> diff --git a/drivers/rtc/rtc-pm8xxx.c b/drivers/rtc/rtc-pm8xxx.c
>> new file mode 100644
>> index 0000000..4694c4e
>> --- /dev/null
>> +++ b/drivers/rtc/rtc-pm8xxx.c
>> +
>> +/**
>> + * struct pm8xxx_rtc	rtc driver internal structure
>
> This is missing a dash '-'.
>
>> +static int pm8xxx_read_wrapper(struct pm8xxx_rtc *rtc_dd, u8 *rtc_val,
>> +		int base, int count)
>> +{
>> +	int i, rc;
>> +	struct device *parent = rtc_dd->rtc_dev->parent;
>> +
>> +	for (i = 0; i<  count; i++) {
>> +		rc = pm8xxx_readb(parent, base + i,&rtc_val[i]);
>> +		if (rc<  0) {
>> +			dev_err(rtc_dd->rtc_dev, "PMIC read failed\n");
>
> I still think these printks are useless when you already have better
> printks at the call sites on the error path.

I actually don't mind seeing the entire error flow in the log. 
pm8xxx_readb() might report a failure but it is sometimes help to know 
who the caller was that may have triggered the error.


-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

      reply	other threads:[~2011-05-26 22:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-05  5:48 [PATCH V2] drivers: rtc: Add support for Qualcomm PMIC8xxx RTC Anirudh Ghayal
2011-05-09 11:41 ` Anirudh Ghayal
2011-05-10  1:44   ` Wan ZongShun
2011-05-10 17:55 ` Stephen Boyd
     [not found]   ` <BANLkTinBpLO-gwdQ1MuL3sqM2MYizTg_EA@mail.gmail.com>
2011-05-13 10:42     ` Ashay Jaiswal
2011-05-26  5:15 ` [PATCH V3] " Anirudh Ghayal
2011-05-26 17:37   ` Stephen Boyd
2011-05-26 22:22     ` Kenneth Heitke [this message]

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=4DDED2A0.2070109@codeaurora.org \
    --to=kheitke@codeaurora.org \
    --cc=aghayal@codeaurora.org \
    --cc=akpm@linux-foundation.org \
    --cc=ashayj@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mcuos.com@gmail.com \
    --cc=rtc-linux@googlegroups.com \
    --cc=sboyd@codeaurora.org \
    /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.