From: Greg Ungerer <gerg@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] m68knommu: Fix typos in Coldfire 5272 DMA debug code
Date: Fri, 22 Jun 2018 10:19:53 +1000 [thread overview]
Message-ID: <ecdf3bdf-6453-0c5f-1a72-b4df7148c867@linux-m68k.org> (raw)
In-Reply-To: <20180621203053.32047-1-geert@linux-m68k.org>
Hi Geert,
On 22/06/18 06:30, Geert Uytterhoeven wrote:
> If DEBUG_DMA is defined:
>
> include/asm/dma.h: In function ‘set_dma_mode’:
> include/asm/dma.h:393: error: ‘dmabp’ undeclared (first use in this function)
> include/asm/dma.h:393: error: (Each undeclared identifier is reported only once
> include/asm/dma.h:393: error: for each function it appears in.)
> include/asm/dma.h: In function ‘set_dma_addr’:
> include/asm/dma.h:424: error: ‘dmawp’ undeclared (first use in this function)
>
> Reported-by: kbuild test robot <fengguang.wu@intel.com>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Acked-by: Greg Ungerer <gerg@linux-m68k.org>
Do you want me to take this via the m68knommu git tree?
Regards
Greg
> ---
> v2:
> - Add Acked-by.
> ---
> arch/m68k/include/asm/dma.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/m68k/include/asm/dma.h b/arch/m68k/include/asm/dma.h
> index b0978a23bad1d7ee..ae2021964e32d36f 100644
> --- a/arch/m68k/include/asm/dma.h
> +++ b/arch/m68k/include/asm/dma.h
> @@ -390,7 +390,7 @@ static __inline__ void set_dma_mode(unsigned int dmanr, char mode)
>
> #ifdef DEBUG_DMA
> printk("%s(%d): dmanr=%d DMR[%x]=%x DIR[%x]=%x\n", __FILE__, __LINE__,
> - dmanr, (int) &dmalp[MCFDMA_DMR], dmabp[MCFDMA_DMR],
> + dmanr, (int) &dmalp[MCFDMA_DMR], dmalp[MCFDMA_DMR],
> (int) &dmawp[MCFDMA_DIR], dmawp[MCFDMA_DIR]);
> #endif
> }
> @@ -421,7 +421,7 @@ static __inline__ void set_dma_addr(unsigned int dmanr, unsigned int a)
>
> #ifdef DEBUG_DMA
> printk("%s(%d): dmanr=%d DMR[%x]=%x SAR[%x]=%08x DAR[%x]=%08x\n",
> - __FILE__, __LINE__, dmanr, (int) &dmawp[MCFDMA_DMR], dmawp[MCFDMA_DMR],
> + __FILE__, __LINE__, dmanr, (int) &dmalp[MCFDMA_DMR], dmalp[MCFDMA_DMR],
> (int) &dmalp[MCFDMA_DSAR], dmalp[MCFDMA_DSAR],
> (int) &dmalp[MCFDMA_DDAR], dmalp[MCFDMA_DDAR]);
> #endif
>
next prev parent reply other threads:[~2018-06-22 0:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 20:30 Geert Uytterhoeven
2018-06-22 0:19 ` Greg Ungerer [this message]
2018-06-22 6:35 ` Geert Uytterhoeven
2018-06-22 7:06 ` Greg Ungerer
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=ecdf3bdf-6453-0c5f-1a72-b4df7148c867@linux-m68k.org \
--to=gerg@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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
all inboxes | Powered by JetHome®