From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: linux-debuggers@vger.kernel.org
Subject: Re: LPC BoF - Linux Kernel Debugging & Drgn
Date: Thu, 19 Sep 2024 06:23:18 -0700 [thread overview]
Message-ID: <87ploz3hh5.fsf@oracle.com> (raw)
In-Reply-To: <8734m7nl8x.fsf@oracle.com>
Hello all,
This will be happening in 20 minutes. Remote users can login at
https://meet.lpc.events, select the "Birds of a Feather" room, and join.
You can also join the matrix room for the BOF room here:
https://matrix.to/#/#bofs:lpc.events
Thanks,
Stephen
Stephen Brennan <stephen.s.brennan@oracle.com> writes:
> Hello everyone!
>
> For those attending Plumbers in-person or virtually, we will be having a
> BoF session where we can get together and discuss debuggers. I'll have
> some interactive demos which should be easy enough in case folks want a
> quick and easy way to get started playing with Drgn, but really it's
> just going to be an attendee-driven discussion. So please show up, bring
> questions, ideas, or things to share of your own!
>
> The BoF is scheduled for 3:45PM CET on Thursday (Sept 19), which is:
>
> 9:45 AM US Eastern
> 6:45 AM US Pacific
>
> This has the nice benefit of avoiding the Toolchain track (Wed) and the
> Perf/Tracing MC (Fri), but it does intersect with some of the BPF MC,
> somewhat unavoidably.
>
> But these times could be subject to change, please check the below
> listing on the LPC schedule in case of any changes.
>
> https://lpc.events/event/18/contributions/1982/
>
> Looking forward to seeing everyone in Vienna or online!
>
> Thanks,
> Stephen
next prev parent reply other threads:[~2024-09-19 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-10 23:26 LPC BoF - Linux Kernel Debugging & Drgn Stephen Brennan
2024-09-19 13:23 ` Stephen Brennan [this message]
2024-09-19 15:14 ` Stephen Brennan
2024-09-19 15:24 ` Stephen Brennan
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=87ploz3hh5.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;
as well as URLs for NNTP newsgroup(s).