From: Greg Ungerer <gregungerer00@gmail.com>
To: Finn Thain <fthain@telegraphics.com.au>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Prevent some compiler warnings in coldfire builds
Date: Sat, 3 Aug 2019 09:36:45 +1000 [thread overview]
Message-ID: <fd5ccd89-987a-3d4b-5c49-9068abadf81d@linux-m68k.org> (raw)
In-Reply-To: <9ec2190f5be1c4e676a803901200364578662b6d.1564704625.git.fthain@telegraphics.com.au>
Hi Finn,
On 2/8/19 10:10 am, Finn Thain wrote:
> Since commit d3b41b6bb49e ("m68k: Dispatch nvram_ops calls to Atari or
> Mac functions"), Coldfire builds generate compiler warnings due to the
> unconditional inclusion of asm/atarihw.h and asm/macintosh.h.
>
> The inclusion of asm/atarihw.h causes warnings like this:
>
> In file included from ./arch/m68k/include/asm/atarihw.h:25:0,
> from arch/m68k/kernel/setup_mm.c:41,
> from arch/m68k/kernel/setup.c:3:
> ./arch/m68k/include/asm/raw_io.h:39:0: warning: "__raw_readb" redefined
> #define __raw_readb in_8
>
> In file included from ./arch/m68k/include/asm/io.h:6:0,
> from arch/m68k/kernel/setup_mm.c:36,
> from arch/m68k/kernel/setup.c:3:
> ./arch/m68k/include/asm/io_no.h:16:0: note: this is the location of the previous definition
> #define __raw_readb(addr) \
> ...
>
> This issue is resolved by dropping the asm/raw_io.h include. It turns out
> that asm/io_mm.h already includes that header file.
>
> Moving the relevant macro definitions helps to clarify this dependency
> and make it safe to include asm/atarihw.h.
>
> The other warnings look like this:
>
> In file included from arch/m68k/kernel/setup_mm.c:48:0,
> from arch/m68k/kernel/setup.c:3:
> ./arch/m68k/include/asm/macintosh.h:19:35: warning: 'struct irq_data' declared inside parameter list will not be visible outside of this definition or declaration
> extern void mac_irq_enable(struct irq_data *data);
> ^~~~~~~~
> ...
>
> This issue is resolved by adding the missing linux/irq.h include.
>
> Cc: Michael Schmitz <schmitzmic@gmail.com>
> Signed-off-by: Finn Thain <fthain@telegraphics.com.au>
> ---
> arch/m68k/include/asm/atarihw.h | 9 ---------
> arch/m68k/include/asm/io_mm.h | 6 +++++-
> arch/m68k/include/asm/macintosh.h | 1 +
> 3 files changed, 6 insertions(+), 10 deletions(-)
>
> diff --git a/arch/m68k/include/asm/atarihw.h b/arch/m68k/include/asm/atarihw.h
> index 533008262b69..5e5601c382b8 100644
> --- a/arch/m68k/include/asm/atarihw.h
> +++ b/arch/m68k/include/asm/atarihw.h
> @@ -22,7 +22,6 @@
>
> #include <linux/types.h>
> #include <asm/bootinfo-atari.h>
> -#include <asm/raw_io.h>
> #include <asm/kmap.h>
>
> extern u_long atari_mch_cookie;
> @@ -132,14 +131,6 @@ extern struct atari_hw_present atari_hw_present;
> */
>
>
> -#define atari_readb raw_inb
> -#define atari_writeb raw_outb
> -
> -#define atari_inb_p raw_inb
> -#define atari_outb_p raw_outb
> -
> -
> -
> #include <linux/mm.h>
> #include <asm/cacheflush.h>
>
> diff --git a/arch/m68k/include/asm/io_mm.h b/arch/m68k/include/asm/io_mm.h
> index 6c03ca5bc436..819f611dccf2 100644
> --- a/arch/m68k/include/asm/io_mm.h
> +++ b/arch/m68k/include/asm/io_mm.h
> @@ -29,7 +29,11 @@
> #include <asm-generic/iomap.h>
>
> #ifdef CONFIG_ATARI
> -#include <asm/atarihw.h>
> +#define atari_readb raw_inb
> +#define atari_writeb raw_outb
> +
> +#define atari_inb_p raw_inb
> +#define atari_outb_p raw_outb
> #endif
>
>
> diff --git a/arch/m68k/include/asm/macintosh.h b/arch/m68k/include/asm/macintosh.h
> index 8f0698bca3dc..8a43babcf53a 100644
> --- a/arch/m68k/include/asm/macintosh.h
> +++ b/arch/m68k/include/asm/macintosh.h
> @@ -4,6 +4,7 @@
>
> #include <linux/seq_file.h>
> #include <linux/interrupt.h>
> +#include <linux/irq.h>
>
> #include <asm/bootinfo-mac.h>
>
Looks good to me:
Acked-by: Greg Ungerer <gerg@linux-m68k.org>
Geert: I can take this via the m68knommu tree if you like?
Or if you want to pick it up then no problem.
Regards
Greg
next prev parent reply other threads:[~2019-08-02 23:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 0:10 [PATCH] m68k: Prevent some compiler warnings in coldfire builds Finn Thain
2019-08-02 0:33 ` Finn Thain
2019-08-02 23:36 ` Greg Ungerer [this message]
2019-08-05 7:14 ` Geert Uytterhoeven
2019-08-05 12:18 ` Greg Ungerer
2019-08-19 11:27 ` Geert Uytterhoeven
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=fd5ccd89-987a-3d4b-5c49-9068abadf81d@linux-m68k.org \
--to=gregungerer00@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitzmic@gmail.com \
/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).