From: Sam Protsenko <semen.protsenko@linaro.org>
To: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
codalist@coda.cs.cmu.edu, coda@cs.cmu.edu
Cc: Jan Harkes <jaharkes@cs.cmu.edu>,
"James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Praneeth Bajjuri <praneeth@ti.com>,
Paul Sokolovsky <paul.sokolovsky@linaro.org>,
Miklos Szeredi <mszeredi@suse.cz>,
Sumit Semwal <sumit.semwal@linaro.org>,
Ruslan Bilovol <ruslan.bilovol@gmail.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: [PATCH 1/2] codafs: Fix build using bare-metal toolchain
Date: Tue, 28 Aug 2018 17:24:20 +0300 [thread overview]
Message-ID: <20180828142421.15335-2-semen.protsenko@linaro.org> (raw)
In-Reply-To: <20180828142421.15335-1-semen.protsenko@linaro.org>
The kernel is self-contained project and can be built with bare-metal
toolchain. But bare-metal toolchain doesn't define u_quad_t type.
Because of this codafs build fails when building with bare-metal
toolchain. This patch fixes it by defining u_quad_t type in case when
non-Linux toolchain is used.
Signed-off-by: Sam Protsenko <semen.protsenko@linaro.org>
---
include/uapi/linux/coda.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/include/uapi/linux/coda.h b/include/uapi/linux/coda.h
index 695fade33c64..098a6c318b0a 100644
--- a/include/uapi/linux/coda.h
+++ b/include/uapi/linux/coda.h
@@ -96,6 +96,11 @@ typedef unsigned long long u_quad_t;
#endif /* !KERNEL */
#endif /* !DJGPP */
+/* Handle bare-metal toolchain case */
+#if defined(__KERNEL__) && !defined(__linux__) && !defined(_UQUAD_T_) && \
+!defined(__UQUAD_TYPE)
+typedef unsigned long long u_quad_t;
+#endif
#if defined(__linux__)
#include <linux/time.h>
--
2.18.0
next prev parent reply other threads:[~2018-08-28 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-28 14:24 [PATCH 0/2] Fix allmodconfig build with " Sam Protsenko
2018-08-28 14:24 ` Sam Protsenko [this message]
2018-08-28 17:03 ` [PATCH 1/2] codafs: Fix build using " Andy Shevchenko
2018-08-28 17:07 ` Andy Shevchenko
2018-08-29 6:33 ` Christoph Hellwig
2018-08-29 14:03 ` Sam Protsenko
2018-08-28 14:24 ` [PATCH 2/2] scsi: aic7xxx: " Sam Protsenko
2018-08-29 6:32 ` Christoph Hellwig
2018-08-29 14:01 ` Sam Protsenko
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=20180828142421.15335-2-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=jaharkes@cs.cmu.edu \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mszeredi@suse.cz \
--cc=paul.sokolovsky@linaro.org \
--cc=praneeth@ti.com \
--cc=ruslan.bilovol@gmail.com \
--cc=sumit.semwal@linaro.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
all inboxes | Powered by JetHome®