From: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
To: "ksummit-discuss-cunTk1MwBs98uUxBSJOaYoYkZiVZrdSR2LY78lusg7I@public.gmane.org"
<ksummit-discuss-cunTk1MwBs98uUxBSJOaYoYkZiVZrdSR2LY78lusg7I@public.gmane.org>,
devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [TECH TOPIC] Devicetree Tooling and Validation
Date: Wed, 2 Aug 2017 15:08:20 +0100 [thread overview]
Message-ID: <CACxGe6sjbZZG=Tai4gYKMrmOnsjXjwp8AEVsuasGMh6WTVHRcg@mail.gmail.com> (raw)
Hi folks,
Late entry: I'd like to propose holding a 1/2 day Devicetree
miniconference at Kernel Summit this year. There is a need to talk
about current proposals on the table for devicetree validation and
tooling options, as well as hammering out better sharing between
projects.
I had originally been planning to do this at Linux Plumbers Conference
13-15 September in LA, but a large number of the key participants will
be in Prague for ELCE, but not in LA for Plumbers.
The Plumbers devicetree wiki page is being used to wrangle specific topics:
http://wiki.linuxplumbersconf.org/2017:device_tree
Cheers,
g.
reply other threads:[~2017-08-02 14:08 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='CACxGe6sjbZZG=Tai4gYKMrmOnsjXjwp8AEVsuasGMh6WTVHRcg@mail.gmail.com' \
--to=grant.likely-s3s/wqlpoipyb63q8fvjnq@public.gmane.org \
--cc=devicetree-spec-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ksummit-discuss-cunTk1MwBs98uUxBSJOaYoYkZiVZrdSR2LY78lusg7I@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).