From: Nick Desaulniers <ndesaulniers@google.com>
To: linux-toolchains@vger.kernel.org
Cc: "Jose E. Marchesi" <jemarch@gnu.org>
Subject: Fwd: Toolchains and Kernel Microconference Accepted into 2021 Linux Plumbers Conference
Date: Thu, 24 Jun 2021 13:43:59 -0700 [thread overview]
Message-ID: <CAKwvOd=eg5UNsRK2X8CnWXnu+GPgB3vZwy+tjbNAebsGjpDJMA@mail.gmail.com> (raw)
In-Reply-To: <CAKwvOd=hysH+Ss4U6vx2k2DB2Y6R7YMYmNpiPPRtDTgaFQ0WCw@mail.gmail.com>
(reposting since I've confused kernel-toolchains with linux-toolchains)
Our MC has been formally accepted:
https://www.linuxplumbersconf.org/blog/2021/index.php/2021/06/21/toolchains-and-kernel-microconference-accepted-into-2021-linux-plumbers-conference/
Would you mind please submitting a formal talk proposal at:
https://www.linuxplumbersconf.org/event/11/abstracts/
In the bottom right, click "Submit new proposal" then make sure to
select "Toolchains and Kernel" under the Track dropdown.
The Content field will be what's shown to attendees. We'd like to
close our CFP by August 14th, 2021.
---------- Forwarded message ---------
From: Nick Desaulniers <ndesaulniers@google.com>
Date: Tue, Jun 22, 2021 at 9:12 AM
Subject: Toolchains and Kernel Microconference Accepted into 2021
Linux Plumbers Conference
To: Jose E. Marchesi <jose.marchesi@oracle.com>
Cc: clang-built-linux <clang-built-linux@googlegroups.com>,
<kernel-toolchains@vger.kernel.org>
https://www.linuxplumbersconf.org/blog/2021/index.php/2021/06/21/toolchains-and-kernel-microconference-accepted-into-2021-linux-plumbers-conference/
--
Thanks,
~Nick Desaulniers
--
Thanks,
~Nick Desaulniers
parent reply other threads:[~2021-06-24 20:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAKwvOd=hysH+Ss4U6vx2k2DB2Y6R7YMYmNpiPPRtDTgaFQ0WCw@mail.gmail.com>]
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='CAKwvOd=eg5UNsRK2X8CnWXnu+GPgB3vZwy+tjbNAebsGjpDJMA@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=jemarch@gnu.org \
--cc=linux-toolchains@vger.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;
as well as URLs for NNTP newsgroup(s).