archive mirror
 help / color / mirror / Atom feed
From: Chen Gang S <>
To: Chen Gang <>,
	"" <>
Subject: Fwd: [PATCH] c6x: Makefile: Add -D__linux__
Date: Tue, 03 Mar 2015 06:46:09 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Just forward mail.

-------- Forwarded Message --------
Subject: [PATCH] c6x: Makefile: Add -D__linux__
Date: Tue, 03 Mar 2015 06:33:42 +0800
From: Chen Gang <>
To: Mark Salter <>,
CC: <>, <>

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 <>
 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

       reply	other threads:[~2015-03-02 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2015-03-02 22:46 ` Chen Gang S [this message]
2015-03-26 14:13 ` [PATCH] c6x: Makefile: Add -D__linux__ Mark Salter

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).