From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: "Jose E. Marchesi via Gdb-patches" <gdb-patches@sourceware.org>
Subject: Re: [RFP] Toolchains and Kernel MC in LPC 2021
Date: Tue, 08 Jun 2021 11:02:33 +0200 [thread overview]
Message-ID: <87wnr4ybiu.fsf@oracle.com> (raw)
In-Reply-To: <87eeemtqht.fsf@oracle.com> (Jose E. Marchesi via Gdb-patches's message of "Tue, 04 May 2021 18:26:06 +0200")
ping.
There is still time to add more topics/key participants to the MC
proposal.
If interested in participating, please let us know in jemarch@gnu.org
and ndesaulniers@google.com.
Thanks!
> Hi people!
>
> This year the Linux Plumbers Conference (https://linuxplumbersconf.org) will
> be fully virtual, and will happend from 20 to 24 September 2021.
>
> As part of the event, we are organizing a `Toolchains and Kernel
> Micro-conference' devoted to discuss specific topics involving kernel and
> toolchain. It will cover both the GNU Toolchain and LLVM.
>
> As in previous years, the emphasis will be in discussing specific topics that
> require collaboration/interaction between the kernel and the toolchain chaps.
> Examples of topics are wrapping of syscalls, specific features in the
> compiler/linker/etc that are used by the kernel, desired optimizations,
> features to alleviate security concerns on the kernel side, and the like.
>
> In order to get the Micro-Conference accepted we need to provide a list of
> both topics and prospective attendants, so thats why I am reaching out to you
> asking for:
>
> 1) Topics your project may want to discuss with the kernel hackers, during the
> event.
>
> 2) Whether you are willing to contribute and/or participate in the
> micro-conference.
>
> Please let me know in jose.marchesi@oracle.com or jemarch@gnu.org.
> Thanks!
prev parent reply other threads:[~2021-06-08 9:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-04 16:26 Jose E. Marchesi
2021-06-08 9:02 ` Jose E. Marchesi [this message]
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=87wnr4ybiu.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=gdb-patches@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).