From: Gustavo Padovan <gus@collabora.com>
To: "Automated Testing" <automated-testing@lists.yoctoproject.org>,
"kernelci lists.linux.dev" <kernelci@lists.linux.dev>,
"Linux Kselftest" <linux-kselftest@vger.kernel.org>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Cc: "Bird, Tim" <tim.bird@sony.com>, "sashal" <sashal@kernel.org>
Subject: Last week to submit your sessions to the Automated Testing Summit!
Date: Tue, 13 May 2025 13:54:25 -0300 [thread overview]
Message-ID: <196ca91a75b.e0a5fd292825092.4995709177992280379@collabora.com> (raw)
In-Reply-To:
Hello,
It is the last week to submit your proposal!
The Automated Testing Summit (ATS) 2025 will be held as a co-located event at the Open Source Summit North America!
https://events.linuxfoundation.org/open-source-summit-north-america/features/co-located-events/#automated-testing-summit-2025
📅 Date: June 26, 2025
📍 Location: Denver, CO, USA
Hosted by KernelCI, ATS is a technical summit focused on the challenges of testing and quality assurance in the Linux ecosystem — especially in upstream kernel development, embedded systems, cloud environments, and CI integration.
This is a great opportunity to share your work on:
* Kernel and userspace test frameworks
* Lab infrastructure and automation
* CI/CD pipelines for Linux
* Fuzzing, performance testing, and debugging tools
* Sharing and standardizing test results across systems
Whether you’re working on kernel testing, running tests on hardware labs, developing QA tools, or building infrastructure that scales across projects, ATS is the place to collaborate and move the ecosystem forward.
Submit your talk by May 18, 2025:
👉 Call for Proposals (CFP): https://sessionize.com/atsna2025
We hope to see you in Denver!
— The KernelCI Team
--
Gustavo Padovan
Collabora Ltd.
next reply other threads:[~2025-05-13 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 16:54 Gustavo Padovan [this message]
2025-05-19 19:20 ` Automated Testing Summit - CFP extended until May 20th Gustavo Padovan
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=196ca91a75b.e0a5fd292825092.4995709177992280379@collabora.com \
--to=gus@collabora.com \
--cc=automated-testing@lists.yoctoproject.org \
--cc=kernelci@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=tim.bird@sony.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
all inboxes | Powered by JetHome®