From: Qian Cai <cai@lca.pw>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Will Deacon <will.deacon@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: "arm64: vdso: Substitute gettimeofday() with C implementation" breaks clang build
Date: Tue, 25 Jun 2019 08:16:04 -0400 [thread overview]
Message-ID: <1561464964.5154.63.camel@lca.pw> (raw)
The linux-next commit "arm64: vdso: Substitute gettimeofday() with C
implementation" [1] breaks clang build.
error: invalid value 'tiny' in '-mcode-model tiny'
make[1]: *** [scripts/Makefile.build:279:
arch/arm64/kernel/vdso/vgettimeofday.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make: *** [arch/arm64/Makefile:180: vdso_prepare] Error 2
[1] https://patchwork.kernel.org/patch/11009663/
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2019-06-25 12:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 12:16 Qian Cai [this message]
2019-06-25 12:47 ` "arm64: vdso: Substitute gettimeofday() with C implementation" breaks clang build Vincenzo Frascino
2019-06-25 12:56 ` Qian Cai
2019-06-25 13:40 ` Vincenzo Frascino
2019-06-25 13:51 ` Qian Cai
2019-06-25 14:11 ` Vincenzo Frascino
2019-06-25 14:28 ` Qian Cai
2019-06-25 14:30 ` Vincenzo Frascino
2019-06-25 14:54 ` Vincenzo Frascino
2019-06-25 15:16 ` Qian Cai
2019-06-25 16:26 ` Nick Desaulniers
2019-06-25 17:00 ` Vincenzo Frascino
2019-06-25 17:31 ` Qian Cai
2019-06-25 17:33 ` Vincenzo Frascino
2019-06-26 9:38 ` Will Deacon
2019-06-26 9:45 ` Vincenzo Frascino
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=1561464964.5154.63.camel@lca.pw \
--to=cai@lca.pw \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vincenzo.frascino@arm.com \
--cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).