From: "Mark Brown" <broonie@kernel.org>
To: kernelci@groups.io, ndesaulniers@google.com
Cc: Kevin Hilman <khilman@baylibre.com>,
Chen Rong <rong.a.chen@intel.com>,
Philip Li <philip.li@intel.com>, Dan Rue <dan.rue@linaro.org>,
clang-built-linux <clang-built-linux@googlegroups.com>,
Mathieu Acher <mathieu.acher@irisa.fr>,
Steven Rostedt <rostedt@goodmis.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: plumbers session on CI and LLVM
Date: Thu, 9 Jul 2020 15:44:44 +0100 [thread overview]
Message-ID: <20200709144444.GE4960@sirena.org.uk> (raw)
In-Reply-To: <CAKwvOd=um1y=Ax2hK5YYQBxbxLK4kiQuDs9fZsr77YyNR5r=Ww@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Wed, Jul 08, 2020 at 12:24:07PM -0700, Nick Desaulniers via groups.io wrote:
> I'm trying to put together a Micro Conference for plumbers focused on
> LLVM. In particular, I'd like to have a session that focuses on
> Continuous Integration (KernelCI, 0day bot, tuxbuild, kernel
> configuration space, and LLVM buildbots).
> I'm curious, are you all planning on attending the conference?
I think most of the KernelCI people will be there.
> If so, would such a session be of interest to attend or speak at?
I'd certainly be interested, I think some of the other Arm people would
be too.
> the LLVM MC, or even if it is of value or not? One thing I'm curious
> is what happens for two concurrent MCs if leads need to attend both?
> Maybe the conference committee can help us avoid such scheduling
> contention?
In the past the organizers have tried to avoid scheduling issues when
they've been highlighted to them. I'm not sure if the conference being
online will make that less of an issue than normal.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-07-09 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-08 19:24 plumbers session on CI and LLVM Nick Desaulniers
2020-07-09 14:44 ` Mark Brown [this message]
2020-07-09 16:19 ` Kevin Hilman
2020-07-10 14:49 ` Mathieu Acher
2020-08-02 3:53 ` Nick Desaulniers
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=20200709144444.GE4960@sirena.org.uk \
--to=broonie@kernel.org \
--cc=clang-built-linux@googlegroups.com \
--cc=dan.rue@linaro.org \
--cc=kernelci@groups.io \
--cc=khilman@baylibre.com \
--cc=mathieu.acher@irisa.fr \
--cc=ndesaulniers@google.com \
--cc=philip.li@intel.com \
--cc=rong.a.chen@intel.com \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
/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