From: "Kevin Hilman" <khilman@baylibre.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: kernelci@groups.io, 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, 09 Jul 2020 09:19:27 -0700 [thread overview]
Message-ID: <7h36603blc.fsf@baylibre.com> (raw)
In-Reply-To: <CAKwvOd=um1y=Ax2hK5YYQBxbxLK4kiQuDs9fZsr77YyNR5r=Ww@mail.gmail.com>
Nick Desaulniers <ndesaulniers@google.com> writes:
> Hi Kevin and folks,
> 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?
Yes, I plan to attend and most KernelCI folks will be there as well as
we'll have a few topics at the testing/fuzzing microconf.
> If so, would such a session be of interest to attend or speak at?
Yes.
> I saw the testing MC has already been approved and that Kevin and
> Sasha are the leads. I'm still working on the approval for our MC so
> it may not happen ultimately, but I still would like to have such a
> session regardless of which MC it's in.
>
> Do folks who are planning to attend such a session have thoughts on
> whether we can carve this out of the existing testing MC vs keep it in
> the LLVM MC, or even if it is of value or not?
If you don't get your approved, feel free to submit to testing/fuzzing,
but it looks to me that doing so would limit the scope of topics you
want to discuss. It sounds to me like you have enough non-CI topics for
your own MC.
> 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?
When you submit your MC you can request to be scheduled separately from
testing/fuzzing so we can attend both.
Kevin
next prev parent reply other threads:[~2020-07-09 16:19 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
2020-07-09 16:19 ` Kevin Hilman [this message]
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=7h36603blc.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=clang-built-linux@googlegroups.com \
--cc=dan.rue@linaro.org \
--cc=kernelci@groups.io \
--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