From: Chen Gang <gang.chen@asianux.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Paul McKenney <paulmck@linux.vnet.ibm.com>,
"dhowells@redhat.com" <dhowells@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
davej@redhat.com, Arnd Bergmann <arnd@arndb.de>,
linux-m68k <linux-m68k@lists.linux-m68k.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] arch: m68k: include: asm: define 'VM_DATA_DEFAULT_FLAGS' no matter whether has 'NOMMU' or not.
Date: Sat, 22 Jun 2013 14:56:27 +0800 [thread overview]
Message-ID: <51C54A9B.9060009@asianux.com> (raw)
In-Reply-To: <51C548E2.1060104@asianux.com>
The same .config file, also report the compiling error below:
drivers/i2c/busses/i2c-ocores.c:81:2: error: implicit declaration of function ‘iowrite8’ [-Werror=implicit-function-declaration]
drivers/i2c/busses/i2c-ocores.c:86:2: error: implicit declaration of function ‘iowrite16’ [-Werror=implicit-function-declaration]
drivers/i2c/busses/i2c-ocores.c:91:2: error: implicit declaration of function ‘iowrite32’ [-Werror=implicit-function-declaration]
drivers/i2c/busses/i2c-ocores.c:96:2: error: implicit declaration of function ‘ioread8’ [-Werror=implicit-function-declaration]
drivers/i2c/busses/i2c-ocores.c:101:2: error: implicit declaration of function ‘ioread16’ [-Werror=implicit-function-declaration]
drivers/i2c/busses/i2c-ocores.c:106:2: error: implicit declaration of function ‘ioread32’ [-Werror=implicit-function-declaration]
Excuse me, I am not quite familiar with the related hardware and m68k,
I guess under m68k architecture, we need not this drivers, is it correct ?
Thanks.
On 06/22/2013 02:49 PM, Chen Gang wrote:
>
> Define 'VM_DATA_DEFAULT_FLAGS' when 'NOMMU' to pass compiling.
>
> So move it from "include/asm/page_mm.h to "include/asm/page.h"
>
> The related make:
>
> make ARCH=m68k randconfig
> make ARCH=m68k menuconfig
> choose cross compiler
> disable MMU support
> make ARCH=m68k V=1 EXTRA_CFLAGS=-W
>
> The related error:
>
> security/selinux/hooks.c: In function �selinux_init�:
> security/selinux/hooks.c:5821:21: error: �VM_DATA_DEFAULT_FLAGS� undeclared (first use in this function)
>
> (the attachment is the related .config file)
>
>
> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
> arch/m68k/include/asm/page.h | 3 +++
> arch/m68k/include/asm/page_mm.h | 3 ---
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/m68k/include/asm/page.h b/arch/m68k/include/asm/page.h
> index 7c360da..38b024a 100644
> --- a/arch/m68k/include/asm/page.h
> +++ b/arch/m68k/include/asm/page.h
> @@ -48,6 +48,9 @@ extern unsigned long _ramend;
> #include <asm/page_no.h>
> #endif
>
> +#define VM_DATA_DEFAULT_FLAGS (VM_READ | VM_WRITE | VM_EXEC | \
> + VM_MAYREAD | VM_MAYWRITE | VM_MAYEXEC)
> +
> #include <asm-generic/getorder.h>
>
> #endif /* _M68K_PAGE_H */
> diff --git a/arch/m68k/include/asm/page_mm.h b/arch/m68k/include/asm/page_mm.h
> index 89f2014..5029f73 100644
> --- a/arch/m68k/include/asm/page_mm.h
> +++ b/arch/m68k/include/asm/page_mm.h
> @@ -173,7 +173,4 @@ static inline __attribute_const__ int __virt_to_node_shift(void)
>
> #endif /* __ASSEMBLY__ */
>
> -#define VM_DATA_DEFAULT_FLAGS (VM_READ | VM_WRITE | VM_EXEC | \
> - VM_MAYREAD | VM_MAYWRITE | VM_MAYEXEC)
> -
> #endif /* _M68K_PAGE_MM_H */
>
--
Chen Gang
Asianux Corporation
next prev parent reply other threads:[~2013-06-22 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-22 6:49 [PATCH] arch: m68k: include: asm: define 'VM_DATA_DEFAULT_FLAGS' no matter whether has 'NOMMU' or not Chen Gang
2013-06-22 6:56 ` Chen Gang [this message]
2013-07-01 2:43 ` Chen Gang
2013-07-01 2:43 ` Chen Gang
2013-08-05 1:37 ` Greg Ungerer
2013-08-05 1:37 ` Greg Ungerer
2013-08-05 2:21 ` Chen Gang F T
2013-08-05 2:21 ` Chen Gang F T
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=51C54A9B.9060009@asianux.com \
--to=gang.chen@asianux.com \
--cc=arnd@arndb.de \
--cc=davej@redhat.com \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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