linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: zhiyong.tao@mediatek.com (zhiyong tao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH -next] iio: adc: mt2701: Remove redundant dev_err call in mt6577_auxadc_probe()
Date: Tue, 30 Aug 2016 09:29:59 +0800	[thread overview]
Message-ID: <1472520599.24148.13.camel@mhfsdcap03> (raw)
In-Reply-To: <88307772-dd0f-a2f2-efd8-6c64a0cb14e4@kernel.org>

On Mon, 2016-08-29 at 19:47 +0100, Jonathan Cameron wrote:
> On 26/08/16 15:26, Wei Yongjun wrote:
> > From: Wei Yongjun <weiyongjun1@huawei.com>
> > 
> > There is a error message within devm_ioremap_resource
> > already, so remove the dev_err call to avoid redundant
> > error message.
> > 
> > Signed-off-by: Wei Yongjun <weiyongjun1@huawei.com>
> Hi Wei,
> 
> I'm not so sure these are actually redundant.  Overly verbose perhaps,
> but they do provide additional information in the log as the
> devm_ioremap_resource doesn't know 'what' has failed, merely how
> it has failed.
> 
> I'm happy to take these, if the driver author / maintainers
> agree, but I'm not keen enough to take them without that.
> 
> Zhiyong Tao, what do you think on this one?
> 
> Jonathan

Dear Jonathan,

Thank you for your suggestion. I think that we can know 'what' has
failed in the driver, if we retain the error message log. It maybe 
advantageous to debug issues.

Zhiyong
> > ---
> >  drivers/iio/adc/mt6577_auxadc.c | 4 +---
> >  1 file changed, 1 insertion(+), 3 deletions(-)
> > 
> > diff --git a/drivers/iio/adc/mt6577_auxadc.c b/drivers/iio/adc/mt6577_auxadc.c
> > index 2d104c8..a268954 100644
> > --- a/drivers/iio/adc/mt6577_auxadc.c
> > +++ b/drivers/iio/adc/mt6577_auxadc.c
> > @@ -206,10 +206,8 @@ static int mt6577_auxadc_probe(struct platform_device *pdev)
> >  
> >  	res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> >  	adc_dev->reg_base = devm_ioremap_resource(&pdev->dev, res);
> > -	if (IS_ERR(adc_dev->reg_base)) {
> > -		dev_err(&pdev->dev, "failed to get auxadc base address\n");
> > +	if (IS_ERR(adc_dev->reg_base))
> >  		return PTR_ERR(adc_dev->reg_base);
> > -	}
> >  
> >  	adc_dev->adc_clk = devm_clk_get(&pdev->dev, "main");
> >  	if (IS_ERR(adc_dev->adc_clk)) {
> > 
> > 
> > 
> 

      reply	other threads:[~2016-08-30  1:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-26 14:26 [PATCH -next] iio: adc: mt2701: Remove redundant dev_err call in mt6577_auxadc_probe() Wei Yongjun
2016-08-29 18:47 ` Jonathan Cameron
2016-08-30  1:29   ` zhiyong tao [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=1472520599.24148.13.camel@mhfsdcap03 \
    --to=zhiyong.tao@mediatek.com \
    --cc=linux-arm-kernel@lists.infradead.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 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).