From: "Mark Brown" <broonie@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: kernelci@groups.io,
Guillaume Tucker <guillaume.tucker@collabora.com>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Todd Kjos <tkjos@google.com>,
android-llvm <android-llvm@googlegroups.com>
Subject: Re: kernelci.org update - 2020-09-23 #minutes
Date: Fri, 25 Sep 2020 14:23:14 +0100 [thread overview]
Message-ID: <20200925132314.GC4841@sirena.org.uk> (raw)
In-Reply-To: <CAKwvOdmEf7jM7QWZcPxy761CGsO24sEDY9OWJJcZKsc6jFy9xA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 647 bytes --]
On Thu, Sep 24, 2020 at 12:25:42PM -0700, Nick Desaulniers wrote:
> On Thu, Sep 24, 2020 at 4:05 AM Mark Brown <broonie@kernel.org> wrote:
> > The thought was that it might be worth using the actual Android
> > toolchains (including all the out of tree patches and whatnot) with
> > these branches as well as upstream clang.
> Would a Docker image containing AOSP LLVM probably be the easiest to
> integrate? If so, I can look at providing such an image.
Yes, a docker image would be great - ideally Debian based. Our current
docker images are built from:
https://github.com/kernelci/kernelci-core/tree/master/jenkins/dockerfiles
FWIW.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-25 13:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 14:50 kernelci.org update - 2020-09-23 #minutes Guillaume Tucker
2020-09-23 21:08 ` Nick Desaulniers
2020-09-23 21:26 ` Guillaume Tucker
2020-09-23 22:06 ` Nick Desaulniers
2020-09-24 11:04 ` Mark Brown
2020-09-24 19:25 ` Nick Desaulniers
2020-09-25 13:23 ` Mark Brown [this message]
2020-09-25 12:39 ` Sedat Dilek
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=20200925132314.GC4841@sirena.org.uk \
--to=broonie@kernel.org \
--cc=android-llvm@googlegroups.com \
--cc=clang-built-linux@googlegroups.com \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci@groups.io \
--cc=ndesaulniers@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox