From: Mark Salter <msalter@redhat.com>
To: Chen Gang <762976180@qq.com>
Cc: a-jacquiot@ti.com,
"linux-c6x-dev@linux-c6x.org" <linux-c6x-dev@linux-c6x.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] c6x: Makefile: Add -D__linux__
Date: Thu, 26 Mar 2015 10:13:00 -0400 [thread overview]
Message-ID: <1427379180.9430.41.camel@deneb.redhat.com> (raw)
In-Reply-To: <54F4E546.9090906@qq.com>
On Tue, 2015-03-03 at 06:33 +0800, Chen Gang wrote:
> For gcc5 c6x raw compiler, at present, it may not define __linux__, so
> c6x kernel still needs to define __linux__ just like another archs have
> done. The related error:
>
> CC [M] fs/coda/psdev.o
> In file included from include/linux/coda.h:64:0,
> from fs/coda/psdev.c:45:
> include/uapi/linux/coda.h:221:2: error: unknown type name 'u_quad_t'
> u_quad_t va_size; /* file size in bytes */
> ^
> include/uapi/linux/coda.h:229:2: error: unknown type name 'u_quad_t'
> u_quad_t va_bytes; /* bytes of disk space held by file */
> ^
> include/uapi/linux/coda.h:230:2: error: unknown type name 'u_quad_t'
> u_quad_t va_filerev; /* file modification number */
> ^
>
> Signed-off-by: Chen Gang <gang.chen.5i5j@gmail.com>
> ---
Thanks! I added this to the c6x tree for next merge window.
> arch/c6x/Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/c6x/Makefile b/arch/c6x/Makefile
> index e72eb34..6b0be67 100644
> --- a/arch/c6x/Makefile
> +++ b/arch/c6x/Makefile
> @@ -8,7 +8,7 @@
>
> KBUILD_DEFCONFIG := dsk6455_defconfig
>
> -cflags-y += -mno-dsbt -msdata=none
> +cflags-y += -mno-dsbt -msdata=none -D__linux__
>
> cflags-$(CONFIG_C6X_BIG_KERNEL) += -mlong-calls
>
prev parent reply other threads:[~2015-03-26 14:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54F4E546.9090906@qq.com>
2015-03-02 22:46 ` Fwd: [PATCH] c6x: Makefile: Add -D__linux__ Chen Gang S
2015-03-26 14:13 ` Mark Salter [this message]
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=1427379180.9430.41.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=762976180@qq.com \
--cc=a-jacquiot@ti.com \
--cc=linux-c6x-dev@linux-c6x.org \
--cc=linux-kernel@vger.kernel.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).