All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Brennan <stephen@brennan.io>
To: linux-debuggers@vger.kernel.org
Subject: Linux Kernel Debugging MC is (still) open: now with a blog post
Date: Sat, 01 Jul 2023 09:49:01 -0700	[thread overview]
Message-ID: <87pm5bvapu.fsf@brennan.io> (raw)

Hi everyone,

Today our post on the LPC blog went live:

https://lpc.events/blog/current/index.php/2023/07/01/linux-kernel-debugging-mc-cfp/

I think it does a good job describing what we're looking for, and it has
instructions for submitting topics. Please consider the problems you
face in your debugging: there's probably a topic for you to submit.

Please also spread the word to other folks and groups who may face the
same debugging problems that we do.

Thanks,
Stephen

                 reply	other threads:[~2023-07-01 17:04 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=87pm5bvapu.fsf@brennan.io \
    --to=stephen@brennan.io \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.