All of lore.kernel.org
 help / color / mirror / Atom feed
From: holler@ahsoftware.de (Alexander Holler)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: davinci: fix build breakage with DEBUG_LL
Date: Tue, 10 Sep 2013 15:36:44 +0200	[thread overview]
Message-ID: <522F206C.7000104@ahsoftware.de> (raw)
In-Reply-To: <1378819415-28666-1-git-send-email-nsekhar@ti.com>

Hello Sekhar,

just what I did here to fix it. So you can add a Tested-By or Acked-By 
if you wish.

Thanks,

Alexander Holler

Am 10.09.2013 15:23, schrieb Sekhar Nori:
> commit fcf7157 ("ARM: davinci: serial: get rid of davinci_uart_config")
> introduced build breakage because of a misplaced
> header file include which cause a bunch of errors when
> the file is included in assembly code (like debug-macro.S)
>
> Fix the build breakage.
>
> Reported-by: Alexander Holler <holler@ahsoftware.de>
> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
> ---
> Applies to latest linus/master
>
>   arch/arm/mach-davinci/include/mach/serial.h |    4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/mach-davinci/include/mach/serial.h b/arch/arm/mach-davinci/include/mach/serial.h
> index 52b8571..ce402cd 100644
> --- a/arch/arm/mach-davinci/include/mach/serial.h
> +++ b/arch/arm/mach-davinci/include/mach/serial.h
> @@ -15,8 +15,6 @@
>
>   #include <mach/hardware.h>
>
> -#include <linux/platform_device.h>
> -
>   #define DAVINCI_UART0_BASE	(IO_PHYS + 0x20000)
>   #define DAVINCI_UART1_BASE	(IO_PHYS + 0x20400)
>   #define DAVINCI_UART2_BASE	(IO_PHYS + 0x20800)
> @@ -39,6 +37,8 @@
>   #define UART_DM646X_SCR_TX_WATERMARK	0x08
>
>   #ifndef __ASSEMBLY__
> +#include <linux/platform_device.h>
> +
>   extern int davinci_serial_init(struct platform_device *);
>   #endif
>
>

  reply	other threads:[~2013-09-10 13:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-10 13:23 [PATCH] ARM: davinci: fix build breakage with DEBUG_LL Sekhar Nori
2013-09-10 13:36 ` Alexander Holler [this message]
2013-09-10 14:50   ` Sekhar Nori

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=522F206C.7000104@ahsoftware.de \
    --to=holler@ahsoftware.de \
    --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.