From: Steven Rostedt <rostedt@goodmis.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
David Malcolm <dmalcolm@redhat.com>,
"Jose E. Marchesi" <jemarch@gnu.org>,
clang-built-linux <llvm@lists.linux.dev>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Plumbers conf presentation on -fanalyze?
Date: Thu, 14 Apr 2022 19:35:37 -0400 [thread overview]
Message-ID: <20220414193537.399dbbb5@rorschach.local.home> (raw)
In-Reply-To: <3119c35ba1fa7247e87d7acb56e85ea99092d0a4.camel@HansenPartnership.com>
On Thu, 14 Apr 2022 19:30:24 -0400
James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> > I didn't see an answer to that question on
> > https://lpc.events/event/16/page/185-faqs.
> > cc' James + Stephen who might be able to answer that more precisely
> > than I could.
>
> It's going to be hybrid ... I thought we actually managed to announce
> that but forgot to put it on the front page. However, there is a
> caveat: to minimize the risk of technical issues, we'd very much like
> the content producers (speakers etc) to be in person. This won't be a
> blanket requirement but we'll be unhappy if you try to have a MC with
> mostly virtual speakers for instance.
Yes, virtual will be mostly for audience participation, as there's so
many things that can go wrong with trying to present at a live event
virtually. This *is* the first time we are doing it, so the unknowns
are limitless.
Having a MC topic with a virtual host is fine, as long as there's
co-hosts that can still be there physically in case there's technical
issues.
-- Steve
next prev parent reply other threads:[~2022-04-14 23:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 21:42 Plumbers conf presentation on -fanalyze? Nick Desaulniers
2022-04-14 22:08 ` David Malcolm
2022-04-14 22:13 ` Nick Desaulniers
2022-04-14 23:30 ` James Bottomley
2022-04-14 23:35 ` Steven Rostedt [this message]
2022-06-21 22:06 ` Nick Desaulniers
2022-06-22 19:12 ` David Malcolm
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=20220414193537.399dbbb5@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=dmalcolm@redhat.com \
--cc=jemarch@gnu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=ndesaulniers@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;
as well as URLs for NNTP newsgroup(s).