From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, ndesaulniers@google.com
Cc: Matt Hart <matthew.hart@linaro.org>, Dan Rue <dan.rue@linaro.org>,
Anmar Oueja <anmar.oueja@linaro.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Todd Kjos <tkjos@google.com>, Sandeep Patil <sspatil@google.com>,
Alistair Delva <adelva@google.com>,
Stephen Hines <srhines@google.com>
Subject: Re: kernel tree support matrix for Clang
Date: Wed, 19 Jun 2019 19:57:14 +0100 [thread overview]
Message-ID: <20190619185714.GY5316@sirena.org.uk> (raw)
In-Reply-To: <CAKwvOd=VBORyjtbqijM8FGAQUV6r6qy3ADQRGrxnKHY_ke=iPw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On Wed, Jun 19, 2019 at 11:04:34AM -0700, Nick Desaulniers via Groups.Io wrote:
> https://travis-ci.com/ClangBuiltLinux/continuous-integration/builds/116089229
>
> Currently 40 targets. They're not partitioned in the UI, but here's
> how I view them:
These appear to mostly be defconfig builds?
> Today KernelCI is covering builds of linux-next with Clang, which is a
> great first step. I think the above list of trees & branches listed
> above for the reasons above are good next steps for KernelCI coverage.
> What do you all think?
The last time we talked about it the plan was to turn clang builds on
for mainline just as soon as the last few patches for making that build
land so that should be after the merge window.
For the stables I did see in at least v4.4 what looked like new
warnings, I'm guessing Greg would take fixes for them but it's probably
better to do do that before enabling anything.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-19 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-19 18:04 kernel tree support matrix for Clang ndesaulniers
2019-06-19 18:57 ` Mark Brown [this message]
2019-06-19 21:12 ` Nick Desaulniers
2019-06-20 11:30 ` Mark Brown
2019-06-25 13:55 ` Matt Hart
2019-06-25 19:45 ` Nick Desaulniers
2019-06-26 11:11 ` Mark Brown
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=20190619185714.GY5316@sirena.org.uk \
--to=broonie@kernel.org \
--cc=adelva@google.com \
--cc=anmar.oueja@linaro.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dan.rue@linaro.org \
--cc=kernelci@groups.io \
--cc=matthew.hart@linaro.org \
--cc=ndesaulniers@google.com \
--cc=srhines@google.com \
--cc=sspatil@google.com \
--cc=tkjos@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.