linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: riscpc: Unbreak the build
Date: Thu, 8 Sep 2022 21:38:51 +0100	[thread overview]
Message-ID: <YxpS2ykp6RSWh08V@shell.armlinux.org.uk> (raw)
In-Reply-To: <20220908203408.2915537-1-bvanassche@acm.org>

On Thu, Sep 08, 2022 at 01:34:08PM -0700, Bart Van Assche wrote:
> This patch fixes the following build error:
> 
> In file included from ./include/linux/io.h:13,
>                  from ./arch/arm/mach-rpc/include/mach/uncompress.h:9,
>                  from arch/arm/boot/compressed/misc.c:31:
> ./arch/arm/include/asm/io.h:85:22: error: conflicting types for ‘__raw_writeb’
>    85 | #define __raw_writeb __raw_writeb
>       |                      ^~~~~~~~~~~~
> ./arch/arm/include/asm/io.h:86:20: note: in expansion of macro ‘__raw_writeb’
>    86 | static inline void __raw_writeb(u8 val, volatile void __iomem *addr)
>       |                    ^~~~~~~~~~~~
> In file included from arch/arm/boot/compressed/misc.c:26:
> arch/arm/boot/compressed/misc-ep93xx.h:13:20: note: previous definition of ‘__raw_writeb’ was here
>    13 | static inline void __raw_writeb(unsigned char value, unsigned int ptr)
>       |                    ^~~~~~~~~~~~
> 
> To: Russell King <linux@armlinux.org.uk>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: linux-arm-kernel@lists.infradead.org
> Fixes: 0361c7e504b1 ("ARM: ep93xx: multiplatform support")
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
>  arch/arm/boot/compressed/misc.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/boot/compressed/misc.c b/arch/arm/boot/compressed/misc.c
> index cb2e069dc73f..abfed1aa2baa 100644
> --- a/arch/arm/boot/compressed/misc.c
> +++ b/arch/arm/boot/compressed/misc.c
> @@ -23,7 +23,9 @@ unsigned int __machine_arch_type;
>  #include <linux/types.h>
>  #include <linux/linkage.h>
>  #include "misc.h"
> +#ifdef CONFIG_ARCH_EP93XX
>  #include "misc-ep93xx.h"
> +#endif
>  
>  static void putstr(const char *ptr);
>  

That'll do. Please put it in the patch system, and I'll get to it maybe
next week sometime. Thanks.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-09-08 20:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 20:34 [PATCH] ARM: riscpc: Unbreak the build Bart Van Assche
2022-09-08 20:38 ` Russell King (Oracle) [this message]
2022-09-08 20:45   ` Bart Van Assche
2022-09-09  6:25     ` Arnd Bergmann
  -- strict thread matches above, loose matches on Subject: below --
2022-09-12 22:13 Bart Van Assche
2022-09-12 21:59 Bart Van Assche
2022-08-30 19:55 Bart Van Assche
2022-08-30 19:58 ` Russell King (Oracle)
2022-08-30 20:55   ` Bart Van Assche
2022-08-30 21:27     ` Russell King (Oracle)
2022-08-31  7:33       ` Arnd Bergmann
2022-08-31 20:56       ` Arnd Bergmann

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=YxpS2ykp6RSWh08V@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=arnd@arndb.de \
    --cc=bvanassche@acm.org \
    --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).