From: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Subject: CFP: Toolchains Track at Linux Plumbers Conf '23
Date: Thu, 15 Jun 2023 11:40:43 -0400 [thread overview]
Message-ID: <CAKwvOdn_OTFCLcQtGB3OSM4XJ8r7=S-gL1SSgMLiPAiTZRucgw@mail.gmail.com> (raw)
(BCC multiple lists)
My colleague Jose Marchesi and I would like to announce that the Call
For Papers (CFP) is now open for the Toolchains Track at Linux
Plumbers Conference 2023.
This year, Plumbers will take place in Richmond Virginia from Monday
November 13th to Wednesday November 15th. Please see
https://lpc.events/event/17/page/198-lpc-2023-overview for more info
about the event.
The aim of the Toolchains track is to fix particular toolchain issues
which are of the interest of the kernel and, ideally, find solutions
in situ, making the best use of the opportunity of live discussion
with kernel developers and maintainers. In particular, this is not
about presenting research nor abstract/miscellaneous toolchain work.
The track will be composed of activities, of variable length depending
on the topic being discussed. Each activity is intended to cover a
particular topic or issue involving both the Linux kernel and one or
more of its associated toolchains and development tools. This includes
compiling, linking, assemblers, debuggers and debugging formats, ABI
analysis tools, object manipulation, etc. Few slides shall be
necessary, and most of the time shall be devoted to actual discussion,
brainstorming and seeking agreement.
To submit a proposal, please visit the below. Click "Submit new
abstract" then make sure to select "Toolchains Track" under the
"Track" dropdown.
https://lpc.events/event/17/abstracts/
Submissions close: 25 September 2023 - Participants notified: 29 September 2023
We look forward to submissions, and hope to see you there!
--
Thanks,
~Nick Desaulniers
reply other threads:[~2023-06-15 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAKwvOdn_OTFCLcQtGB3OSM4XJ8r7=S-gL1SSgMLiPAiTZRucgw@mail.gmail.com' \
--to=ndesaulniers@google.com \
--cc=jose.marchesi@oracle.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 read-only IMAP folder(s) and NNTP newsgroup(s).