From: "Mark Brown" <broonie@kernel.org>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: kernelci@groups.io, 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: Thu, 20 Jun 2019 12:30:16 +0100 [thread overview]
Message-ID: <20190620113016.GB5316@sirena.org.uk> (raw)
In-Reply-To: <CAKwvOd=9U9Z2w8R_GnAKf438f+fXUZ5zCnvsmJGSKnjv+L4g2A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
On Wed, Jun 19, 2019 at 02:12:53PM -0700, Nick Desaulniers wrote:
> On Wed, Jun 19, 2019 at 11:57 AM Mark Brown <broonie@kernel.org> wrote:
> > 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.
> Which merge window? 5.1 or 5.2?
I can't remember off the top of my head; in any case v5.1 is released
so the v5.2 merge window has passed if everything is in there.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-06-20 11:30 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
2019-06-19 21:12 ` Nick Desaulniers
2019-06-20 11:30 ` Mark Brown [this message]
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=20190620113016.GB5316@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.