From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: linux-debuggers@vger.kernel.org
Subject: LPC: Linux Debuggers MC - Submissions Open
Date: Tue, 20 Jun 2023 11:03:18 -0700 [thread overview]
Message-ID: <87sfamvwnt.fsf@oracle.com> (raw)
Hello everyone!
I'm pleased to share that there will be a "Linux Debugging"
microconference at Linux Plumbers (LPC), November 13-15 in Richmond,
Virginia.
The microconference format is a great way for us to get together and
share the ongoing work that could use some discussion and development as
a group. If you've been joining our meetings or following along, or
doing some cool hacking on any of the Linux debugging tools out there,
I'd encourage you to write out your problem statement and submit it to
the Call for Proposals here[1]. Use the "Submit Abstract" button and be
sure to select "Linux Kernel Debugging MC" for your track.
Please do reach out with any questions!
Thanks,
Stephen
[1]: https://lpc.events/event/17/abstracts/
next reply other threads:[~2023-06-20 18:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 18:03 Stephen Brennan [this message]
2023-06-20 19:10 ` LPC: Linux Debuggers MC - Submissions Open Guilherme G. Piccoli
2023-06-20 20:31 ` Stephen Brennan
2023-06-20 20:45 ` Guilherme G. Piccoli
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=87sfamvwnt.fsf@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=linux-debuggers@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