All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, ndesaulniers@google.com
Cc: Guillaume Tucker <guillaume.tucker@collabora.com>,
	clang-built-linux <clang-built-linux@googlegroups.com>,
	Todd Kjos <tkjos@google.com>
Subject: Re: kernelci.org update - 2020-09-23 #minutes
Date: Thu, 24 Sep 2020 12:04:02 +0100	[thread overview]
Message-ID: <20200924110402.GB4754@sirena.org.uk> (raw)
In-Reply-To: <CAKwvOdmAev4-AP3g0cgZ8rV+iR4ACuy1ZQ_XoD09c1d2GF1S7Q@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 913 bytes --]

On Wed, Sep 23, 2020 at 03:06:52PM -0700, Nick Desaulniers via groups.io wrote:
> On Wed, Sep 23, 2020 at 2:26 PM Guillaume Tucker

> > > android-mainline
> > > android12-5.4
> > > android-4.19-stable

> > > are the 3 newest branches that I know of.

> > And which LLVM/Clang versions should be used to build those?

> Will likely be clang-12 (or possibly clang-13).  Those branches are
> basically the kernel branches for "S" which will be released next
> year.  So they are building with a pre-clang-11 right now, but we're
> about to upgrade them to something closer to ToT soon.  Once the "S"
> release of Android is closer, then we will lock down the toolchain
> used for these kernels, but it's sure to change between now and then.

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.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-09-24 11:04 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 [this message]
2020-09-24 19:25         ` Nick Desaulniers
2020-09-25 13:23           ` Mark Brown
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=20200924110402.GB4754@sirena.org.uk \
    --to=broonie@kernel.org \
    --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 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.