From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: shuah <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
"kernelci@lists.linux.dev" <kernelci@lists.linux.dev>
Cc: Shuah Khan <skhan@linuxfoundation.org>, Sasha Levin <sashal@kernel.org>
Subject: Re: [ANNOUNCE/CFP] Kernel Testing & Dependability Micro-conference at LPC 2023
Date: Fri, 21 Jul 2023 19:16:39 +0200 [thread overview]
Message-ID: <e185087d-8df2-2457-0c93-4b638fdee05c@collabora.com> (raw)
In-Reply-To: <e04d1d5b-518b-bebd-aa7a-70b87bc4e867@kernel.org>
+kernelci
On 19/07/2023 23:34, shuah wrote:
> Hello,
>
> I am reaching out to announce that we are once again planning to
> gather to discuss testing and dependability related topics at the
> Kernel Testing & Dependability Micro-conference at LPC 2023.
>
> We invite you to submit proposals for discussion:
> - https://lpc.events/event/17/abstracts/1430/
>
> The Linux Plumbers 2023 Kernel Testing & Dependability track focuses on
> advancing the current state of testing of the Linux Kernel and its related
> infrastructure. The main purpose is to improve software quality and
> dependability for applications that require predictability and trust.
>
> We aim to create connections between folks working on similar projects,
> and help individual projects make progress.
>
> This track is intended to promote collaboration between all the communities
> and people interested in the Kernel testing & dependability. This will help
> move the conversation forward from where we left off at the LPC 2022 Kernel
> Testing & Dependability MC.
>
> We ask that any topic discussions focus on issues/problems they are facing
> and possible alternatives to resolving them. The Micro-conference is open to
> all topics related to testing on Linux, not necessarily in the kernel space.
>
> Suggested topics:
>
> - KernelCI: Topics on improvements and enhancements for test coverage
> - Growing KCIDB, integrating more sources (https://kernelci.org/docs/kcidb/)
> - Sanitizers
> - Using Clang for better testing coverage
> - How to spread KUnit throughout the kernel?
> - Building and testing in-kernel Rust code.
> - Explore ways to improve testing framework and tests in the kernel
> with a specific goal to increase traceability and code coverage.
> - Explore how do SBOMs figure into dependability?
>
> Proposals can be submitted here, by August 20th:
> - https://lpc.events/event/17/abstracts/
>
> Please reach out to MC leads:
> Shuah Khan (shuah@kernel.org)
> Sasha Levin <sashal@kernel.org>
> Guillaume Tucker <guillaume.tucker@collabora.com>
>
> thank you,
> -- Shuah
next prev parent reply other threads:[~2023-07-21 17:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 21:34 [ANNOUNCE/CFP] Kernel Testing & Dependability Micro-conference at LPC 2023 shuah
2023-07-21 17:16 ` Guillaume Tucker [this message]
2023-08-25 17:58 ` shuah
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=e185087d-8df2-2457-0c93-4b638fdee05c@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.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