From: "Jose E. Marchesi via Gdb" <gdb@sourceware.org>
To: gdb@sourceware.org
Subject: LAST REMINDER: CFP deadline for LPC Toolchains Track is today
Date: Fri, 24 Jul 2026 13:12:52 +0200 [thread overview]
Message-ID: <871pcswsi3.fsf@gnu.org> (raw)
Hello people!
Today EOB is the deadline for submitting activities for the Toolchains
Track at Linux Plumbers 2026, which will be held Monday 5 October in
Prague, the day after Cauldron ends.
Submission link: https://lpc.events/event/20/abstracts/
Salud!
---
Submissions close: July 24, 2026 - Speakers notified: from July 31, 2026
The purpose of the Toolchains Track is to work on particular problems or
issues involving development tools (compilers, assemblers, debuggers,
debugging formats, manipulation of binaries, etc) and the Linux kernel,
making the best use of live discussions with kernel developers and
maintainers. This covers both the GNU toolchain and clang/LLVM.
This track is not about presenting research or abstracts, nor
miscellaneous toolchain work. We welcome activities, of variable length
depending on the topic being discussed, devoted to actual discussion,
brainstorming and seeking agreement. Few if any slides shall be
necessary.
Please come and join us in the discussion.
---
reply other threads:[~2026-07-24 11:15 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=871pcswsi3.fsf@gnu.org \
--to=gdb@sourceware.org \
--cc=jemarch@gnu.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