From: Krzysztof Kozlowski <krzk@kernel•org>
To: devicetree@vger•kernel.org, linux-arm-kernel@lists•infradead.org,
linux-arm-msm@vger•kernel.org, Rob Herring <robh@kernel•org>,
Conor Dooley <conor@kernel•org>,
imx@lists•linux.dev, linux-kernel@vger•kernel.org,
devicetree-compiler@vger•kernel.org,
devicetree-spec@vger•kernel.org
Subject: [ANNOUNCEMENT / CFP] LPC 2026 Devicetree Microconference CFP
Date: Tue, 19 May 2026 14:28:53 +0200 [thread overview]
Message-ID: <1668071d-6e18-4379-bf44-b82065731148@kernel.org> (raw)
Hey there,
There will be a dedicated Devicetree Microconference on Linux Plumbers
2026 in October in Prague. Call For Papers is currently open.
https://lpc.events/event/20/contributions/2317/
The Devicetree Microconference focuses on discussing and solving
problems present in the systems using Devicetree as firmware
representation. This notably is Linux kernel and U-Boot, which share the
Devicetree bindings and sources, but also can cover topics relevant to
Zephyr or System Devicetrees.
Topics suggested for discussion are mentioned in "Ongoing problems" in
session description (link above), but of course are not limited to
these. Topics should obviously follow standard Microconference
expectation, that is to be discussion oriented.
We discuss and try to solve actual problems, thus if one wants to
present his new patchset, then that patchset must have been already
reviewed on the list with inconclusive result thus having another
discussing in person would be beneficial.
Allocated time per slot will be between 15 to 30 minutes (20 minutes
last year).
CFP end is not fixed yet, but it will be some time after end of "Kernel
Summit" CFP, so *probably middle of July*. I will confirm that later.
Proposals can be submitted here:
https://lpc.events/event/20/abstracts/
Please remember to choose "Devicetree MC" as the track.
Best regards,
Krzysztof
reply other threads:[~2026-05-19 12:29 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=1668071d-6e18-4379-bf44-b82065731148@kernel.org \
--to=krzk@kernel$(echo .)org \
--cc=conor@kernel$(echo .)org \
--cc=devicetree-compiler@vger$(echo .)kernel.org \
--cc=devicetree-spec@vger$(echo .)kernel.org \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=imx@lists$(echo .)linux.dev \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=robh@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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