From: Omar Sandoval <osandov@osandov.com>
To: linux-debuggers@vger.kernel.org
Subject: Linux Kernel Debugging Tools Monthly Meeting on Wednesday, June 28th
Date: Tue, 27 Jun 2023 13:05:12 -0700 [thread overview]
Message-ID: <ZJtA+PV/ZMxOCnqp@telecaster> (raw)
Hello! The next Linux Kernel Debugging Tools meeting is tomorrow,
Wednesday, June 28nd at 11:30 AM Pacific time. This meeting is a forum
to discuss development of Linux kernel debugging tools like drgn, crash,
and more. I'm back from my parental leave, so I'll be hosting again
(thanks, Stephen, for hosting while I was out).
The agenda so far is:
- The Linux Kernel Debugging microconference was accepted for Linux Plumbers.
Please submit talk proposals! We can discuss what people are planning
to present.
- ORC format changes (see https://github.com/osandov/drgn/issues/303).
- Upcoming drgn release.
Feel free to reply with anything else you'd like to add to the agenda.
If you would like to attend, please email me offlist.
Thanks!
Omar
next reply other threads:[~2023-06-27 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 20:05 Omar Sandoval [this message]
2023-06-28 20:19 ` Linux Kernel Debugging Tools Monthly Meeting on Wednesday, June 28th Omar Sandoval
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=ZJtA+PV/ZMxOCnqp@telecaster \
--to=osandov@osandov.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;
as well as URLs for NNTP newsgroup(s).