From: Rob Herring <robh@kernel.org>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Kumar Gala <kumar.gala@linaro.org>,
Sean Hudson <darknighte@darknighte.com>,
"ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Rob Herring <rob.herring@linaro.org>,
"devicetree-spec@vger.kernel.org"
<devicetree-spec@vger.kernel.org>,
Kanta Vekaria <kanta.vekaria@linaro.org>,
Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
Andy Gross <andy.gross@linaro.org>,
Lucas Stach <l.stach@pengutronix.de>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Ksummit-discuss] Notes & Slides from Devicetree Workshop at Kernel Summit Prague (26 Oct 2017)
Date: Mon, 30 Oct 2017 12:49:04 -0500 [thread overview]
Message-ID: <CAL_Jsq+rZ6nNJnxNq6mrGEeb6RLmyAhG4V+K8uqG_irDR_BCsA@mail.gmail.com> (raw)
In-Reply-To: <CACxGe6tfRByeJrp43Taj166K4Ni0KjmZkC=Xc1pz2=ga6fvDZQ@mail.gmail.com>
On Mon, Oct 30, 2017 at 11:01 AM, Grant Likely
<grant.likely@secretlab.ca> wrote:
> Thank you to everyone who attended the Devicetree Workshop as part of
> the 2017 Kernel Summit in Prague last week. I heard lots of good
> feedback, and I'm already thinking about how to organize next year's
> gathering.
>
> Slides and notes have been uploaded to elinux.org. A summary of the
> topics and next steps still needs to be written. You can find the
> notes and slides here:
>
> https://elinux.org/Device_tree_future#Kernel_Summit_2017.2C_Devicetree_Workshop
Grant, your slides are from 2016 LPC. Is that the right deck? (It's
also ODP, not PDF as labeled in the wiki.)
>From the notes, I don't get a sense if there's some direction on JSON
Schema vs. eBPF. Any comments on that.
Rob
next prev parent reply other threads:[~2017-10-30 17:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 16:01 Grant Likely
2017-10-30 16:11 ` Frank Rowand
2017-10-30 16:15 ` Grant Likely
2017-10-30 17:49 ` Rob Herring [this message]
2017-10-30 22:08 ` Grant Likely
2017-10-31 11:03 ` Pantelis Antoniou
2017-11-02 12:21 ` Matthias Brugger
2017-11-02 13:39 ` Grant Likely
2017-11-02 16:02 ` Frank Rowand
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=CAL_Jsq+rZ6nNJnxNq6mrGEeb6RLmyAhG4V+K8uqG_irDR_BCsA@mail.gmail.com \
--to=robh@kernel.org \
--cc=andy.gross@linaro.org \
--cc=darknighte@darknighte.com \
--cc=david@gibson.dropbear.id.au \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=kanta.vekaria@linaro.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=kumar.gala@linaro.org \
--cc=l.stach@pengutronix.de \
--cc=pantelis.antoniou@konsulko.com \
--cc=rob.herring@linaro.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