From: Sam Protsenko <semen.protsenko@linaro.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
codalist@coda.cs.cmu.edu, coda@cs.cmu.edu,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Praneeth Bajjuri <praneeth@ti.com>
Subject: [PATCH v2] codafs: Fix build using bare-metal toolchain
Date: Mon, 29 Oct 2018 22:03:11 +0200 [thread overview]
Message-ID: <20181029200311.16947-1-semen.protsenko@linaro.org> (raw)
The kernel is self-contained project and can be built with bare-metal
toolchain. But bare-metal toolchain doesn't define __linux__. Because of
this u_quad_t type is not defined when using bare-metal toolchain and
codafs build fails. This patch fixes it by defining u_quad_t type
unconditionally.
Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
---
include/linux/coda.h | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/include/linux/coda.h b/include/linux/coda.h
index d30209b9cef8..0ca0c83fdb1c 100644
--- a/include/linux/coda.h
+++ b/include/linux/coda.h
@@ -58,8 +58,7 @@ Mellon the rights to redistribute these changes without encumbrance.
#ifndef _CODA_HEADER_
#define _CODA_HEADER_
-#if defined(__linux__)
typedef unsigned long long u_quad_t;
-#endif
+
#include <uapi/linux/coda.h>
#endif
--
2.19.1
next reply other threads:[~2018-10-29 20:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 20:03 Sam Protsenko [this message]
2018-10-29 20:05 ` [PATCH v2] codafs: Fix build using bare-metal toolchain Sam Protsenko
2018-10-29 20:08 ` Andy Shevchenko
2018-10-30 6:34 ` Greg KH
2018-10-30 12:01 ` Sam Protsenko
2018-10-30 13:04 ` Jan Harkes
2018-10-30 18:33 ` Sam Protsenko
2018-10-30 18:39 ` Andy Shevchenko
2018-11-23 20:07 ` Andy Shevchenko
2018-11-26 14:35 ` Sam Protsenko
-- strict thread matches above, loose matches on Subject: below --
2018-10-30 20:27 Sam Protsenko
2018-11-21 16:31 ` Sam Protsenko
2018-11-21 16:41 ` Andy Shevchenko
2018-11-21 16:57 ` Christoph Hellwig
2018-11-21 18:10 ` Jan Harkes
2018-11-21 19:36 ` Sam Protsenko
2018-11-21 19:39 ` Sam Protsenko
2018-11-21 22:48 ` Jan Harkes
2019-01-09 15:45 ` Sam Protsenko
2018-11-22 11:32 ` Andy Shevchenko
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=20181029200311.16947-1-semen.protsenko@linaro.org \
--to=semen.protsenko@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=coda@cs.cmu.edu \
--cc=codalist@coda.cs.cmu.edu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=praneeth@ti.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