public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Mason <slash.tmp@free.fr>
To: Ludovic Desroches <ludovic.desroches@atmel.com>
Cc: wsa@the-dreams.de, linux-i2c@vger.kernel.org, nicolas.ferre@atmel.com
Subject: Re: [PATCH] i2c: at91: change log when dma configuration fails
Date: Fri, 13 May 2016 11:53:09 +0200	[thread overview]
Message-ID: <5735A405.3080008@free.fr> (raw)
In-Reply-To: <1463131331-6136-1-git-send-email-ludovic.desroches@atmel.com>

On 13/05/2016 11:22, Ludovic Desroches wrote:

> When the DMA configuration fails, there is a log reporting that we can't
> use DMA and indicating the error number. When booting the kernel, it is
> annoying to see this error number. Moreover, people can think something
> is going wrong. It is not the case, it means that DMA can't be used but
> it doesn't prevent to use i2c.
> 
> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> ---
>  drivers/i2c/busses/i2c-at91.c | 4 +++-
>  1 file changed, 3 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
> index 921d32b..f2a7457 100644
> --- a/drivers/i2c/busses/i2c-at91.c
> +++ b/drivers/i2c/busses/i2c-at91.c
> @@ -1013,7 +1013,9 @@ static int at91_twi_configure_dma(struct at91_twi_dev *dev, u32 phy_addr)
>  
>  error:
>  	if (ret != -EPROBE_DEFER)
> -		dev_info(dev->dev, "can't use DMA, error %d\n", ret);
> +		dev_info(dev->dev,
> +			 "can't request DMA channels, continue without DMA support\n",
> +			 ret);

Did you forget to remove 'ret' after removing the %d format spec?

Regards.

  reply	other threads:[~2016-05-13  9:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13  9:22 [PATCH] i2c: at91: change log when dma configuration fails Ludovic Desroches
2016-05-13  9:53 ` Mason [this message]
2016-05-13 11:48   ` Ludovic Desroches

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=5735A405.3080008@free.fr \
    --to=slash.tmp@free.fr \
    --cc=linux-i2c@vger.kernel.org \
    --cc=ludovic.desroches@atmel.com \
    --cc=nicolas.ferre@atmel.com \
    --cc=wsa@the-dreams.de \
    /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