ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	devicetree-spec@vger.kernel.org,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	David Gibson <david@gibson.dropbear.id.au>,
	Julia Lawall <Julia.Lawall@lip6.fr>,
	Pantelis Antoniou <pantelis.antoniou@konsulko.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	Kumar Gala <kumar.gala@linaro.org>,
	Andy Gross <andy.gross@linaro.org>,
	Rob Herring <rob.herring@linaro.org>,
	Frank Rowand <frowand.list@gmail.com>,
	Sean Hudson <darknighte@darknighte.com>,
	Kanta Vekaria <kanta.vekaria@linaro.org>
Subject: [Ksummit-discuss] Notes & Slides from Devicetree Workshop at Kernel Summit Prague (26 Oct 2017)
Date: Mon, 30 Oct 2017 16:01:07 +0000	[thread overview]
Message-ID: <CACxGe6tfRByeJrp43Taj166K4Ni0KjmZkC=Xc1pz2=ga6fvDZQ@mail.gmail.com> (raw)

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

I also have an audio recording of the entire day, but they are large
audio files (100-200MB each) and I haven't decided how to publish them
yet.

Particular thanks to everyone who helped take notes (Sadly, I didn't
grab the list of names before they disappeared from Etherpad, so the
only person I can thank by name is Julia Lawall who emailed me notes
separately). Also thanks to Sean Hudson for taking care of sound and
to Frank Roland for running microphones around the room. Finally, a
big thank you to the Linux Foundation staff who sorted out all of the
hotel logistics for us.

Please look at the notes to check for accuracy, and I would appreciate
any volunteers to help write up the summary for the day.

I'll post the group photo as soon as I receive it.

Cheers,
g.

             reply	other threads:[~2017-10-30 16:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 16:01 Grant Likely [this message]
2017-10-30 16:11 ` Frank Rowand
2017-10-30 16:15   ` Grant Likely
2017-10-30 17:49 ` Rob Herring
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='CACxGe6tfRByeJrp43Taj166K4Ni0KjmZkC=Xc1pz2=ga6fvDZQ@mail.gmail.com' \
    --to=grant.likely@secretlab.ca \
    --cc=Julia.Lawall@lip6.fr \
    --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=frowand.list@gmail.com \
    --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