All of lore.kernel.org
 help / color / mirror / Atom feed
From: stefan.wahren@i2se.com (Stefan Wahren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: bcm2835: fix typo in legacy-mode warning message
Date: Thu, 21 Apr 2016 17:20:07 +0200	[thread overview]
Message-ID: <5718EFA7.30504@i2se.com> (raw)
In-Reply-To: <1461230641-20317-1-git-send-email-kernel@martin.sperl.org>

Hi Martin,

Am 21.04.2016 um 11:24 schrieb kernel at martin.sperl.org:
> From: Martin Sperl <kernel@martin.sperl.org>
>
> Fix typo in warning message that there is no "interrupt-names"
> property defined in the device-tree and legacy-mode is used.
>
> Signed-off-by: Martin Sperl <kernel@martin.sperl.org>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
> ---
>  drivers/dma/bcm2835-dma.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/dma/bcm2835-dma.c b/drivers/dma/bcm2835-dma.c
> index 9740151..d724393 100644
> --- a/drivers/dma/bcm2835-dma.c
> +++ b/drivers/dma/bcm2835-dma.c
> @@ -974,7 +974,7 @@ static int bcm2835_dma_probe(struct platform_device *pdev)
>  
>  		/* legacy device tree case handling */
>  		dev_warn_once(&pdev->dev,
> -			      "missing interrupts-names property in device tree - legacy interpretation is used");
> +			      "missing interrupt-names property in device tree - legacy interpretation is used");

does it also misses a newline at the end?

>  		/*
>  		 * in case of channel >= 11
>  		 * use the 11th interrupt and that is shared

      reply	other threads:[~2016-04-21 15:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21  9:24 [PATCH] dmaengine: bcm2835: fix typo in legacy-mode warning message kernel at martin.sperl.org
2016-04-21 15:20 ` Stefan Wahren [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=5718EFA7.30504@i2se.com \
    --to=stefan.wahren@i2se.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 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.