linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@baylibre.com>
To: automated-testing@yoctoproject.org,
	linux-kselftest@vger.kernel.org,
	syzkaller <syzkaller@googlegroups.com>
Cc: Sasha Levin <sashal@kernel.org>
Subject: CFP open for testing/fuzzing microconference at LPC
Date: Fri, 24 Jul 2020 12:14:50 -0700	[thread overview]
Message-ID: <7heep067yt.fsf@baylibre.com> (raw)

Hello Linux testing enthusiasts,

The CFP is open for the testing/fuzzing microconference[1] at Linux
plumbers conference.

Please submit your ideas for discussion topics usin the LPC CFP tool:

   https://www.linuxplumbersconf.org/event/7/abstracts/

Click "Submit new Proposal" at the bottom of the page.

There are some suggested topics in the MC announcement[1], but feel
free to submit ideas that are not on that list.

And yes, LPC will be virtual this year as announced on the LPC blog:
https://www.linuxplumbersconf.org/blog/2020/linux-plumbers-conference-2020-goes-virtual/

The tools and logistics are being actively worked on, so stay tuned to
the LPC blog for all the details.

Thanks,

Kevin

[1] From: https://www.linuxplumbersconf.org/event/7/page/80-accepted-microconferences#tf-cr

The Testing and Fuzzing microconference focuses on advancing the current
state of testing and validation of the Linux Kernel, with a focus on
encouraging and facilitating collaboration between testing projects.

Suggested Topics:

    Next steps for KernelCI (data formats, dashboards, etc)
    Structured data feeds for cross-project collaboration
    Integration with kernel.org tools (e.g. b4)
    Continued defragmentation of testing infrastructure
    Better sanitizers: KASAN improvements, KCSAN fallout, future plans.
    Better hardware testing, hardware sanitizers: how the USB fallout was handled, are there efforts to poke at something besides USB?
    Improving real-time testing: is there any testing for real time at all?

MC leads

    Sasha Levin <sashal@kernel.org>
    Kevin Hilman <khilman@kernel.org>

             reply	other threads:[~2020-07-24 19:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24 19:14 Kevin Hilman [this message]
2020-07-31 16:14 ` CFP open for testing/fuzzing microconference at LPC Dmitry Vyukov
2020-07-31 17:05   ` Kevin Hilman

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=7heep067yt.fsf@baylibre.com \
    --to=khilman@baylibre.com \
    --cc=automated-testing@yoctoproject.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=sashal@kernel.org \
    --cc=syzkaller@googlegroups.com \
    /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).