ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Grant Likely <grant.likely@secretlab.ca>,
	"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>
Subject: Re: [Ksummit-discuss] Devicetree Workshop at Kernel Summit Prague (26 Oct 2017)
Date: Mon, 16 Oct 2017 17:42:31 +0100	[thread overview]
Message-ID: <7384dfc6-1068-eb6a-ae5f-7e805be8c48e@codethink.co.uk> (raw)
In-Reply-To: <CACxGe6sxKzNKZbdGA-G=Th2oHwuanyC2kGYuaFcKbSRkuhep+Q@mail.gmail.com>

On 09/10/17 21:39, Grant Likely wrote:
> Kernel Summit is now just over 2 weeks away and it is time to pull
> together the schedule for the Devicetree workshop. Originally I
> planned on just an afternoon, but I've got the room for the whole day,
> so I've got a lot of flexibility on the schedule. Unscheduled time can
> be used for hacking.
> 
> Date: 26 Oct 2017
> Time: 9:00am-5:30pm (Lunch from 12:30-2:30)
> Location: Athens room - Hilton Prague
> 
> If you plan to attend, make sure you update your OSSunmitE/ELCE
> registration to include the DT Workshop (log in to access and modify
> your registration):
> 
> https://www.regonline.com/register/login.aspx?eventID=1883377&MethodId=0&EventsessionId=&Email_Address=&membershipID=
> 
> Here is my current list of topics in no particular order, including
> the topic moderator:
> 
> Runtime memory consumption (Rob Herring)
> Overlay maintenance plan (TBC)
> Stable ABI for devicetree (TBC)
> DT YAML encoding (Pantelis Antoniou)
> DT Schema format - option 1 (Pantelis Antoniou)
> DT Schema format - option 2 (Grant Likely)
> Sharing Generic bindings (TBC)
> devicetree.org update (Grant)
> 
> Reply to this email if you want to propose another topic.

I'd like to see a "device-tree overview" comprising of at-least

- where is dt at
- where is dt going


I am also interested in an
"are we actually solving enough of the old board file problems"

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

  parent reply	other threads:[~2017-10-16 16:42 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-09 20:39 Grant Likely
2017-10-14 12:34 ` Thomas Petazzoni
2017-10-17 13:30   ` Grant Likely
2017-10-16  5:36 ` Michal Simek
2017-10-16 14:11   ` Rob Herring
2017-10-18 14:04     ` Michal Simek
2017-10-18 14:28       ` Andre Przywara
2017-10-18 15:32         ` Rob Herring
2017-10-18 16:05           ` Andre Przywara
2017-10-18 16:20             ` Pantelis Antoniou
2017-10-16 16:40   ` Ben Dooks
2017-10-16 18:44     ` Heiko Stübner
2017-10-16 19:45     ` Rob Herring
2017-10-17 13:38       ` Grant Likely
2017-10-17 23:45         ` Frank Rowand
2017-10-17 13:32   ` Grant Likely
2017-10-18 10:08     ` Thomas Petazzoni
2017-10-16 16:42 ` Ben Dooks [this message]
2017-10-17 13:34   ` Grant Likely
2017-10-17  9:48 ` Boris Brezillon
2017-10-17 13:21   ` Tom Rini
2017-10-17 13:48   ` Grant Likely
2017-10-17 16:21     ` Ian Lepore
2017-10-17 17:02       ` Kumar Gala
2017-10-17 17:24         ` Geert Uytterhoeven
2017-10-17 19:03           ` Bird, Timothy
2017-10-18 12:14             ` Grant Likely
2017-10-18 12:59               ` Pantelis Antoniou
2017-10-18 13:18                 ` Alexandre Belloni
2017-10-18 13:21                   ` Geert Uytterhoeven
2017-10-18 17:41                     ` Bird, Timothy
2017-10-18 18:00                       ` Rob Herring
2017-10-18 21:10                       ` Alexandre Belloni
2017-10-18 16:18                   ` David Woodhouse
2017-10-18 14:13                 ` Rob Herring
2017-10-18 17:45                   ` Bird, Timothy
2017-10-18 14:07           ` Kumar Gala
2017-10-17 17:25       ` Rob Herring
2017-10-18 10:11       ` Thomas Petazzoni
2017-10-18 10:35   ` Chen-Yu Tsai
2017-10-18 11:09     ` Mark Brown
2017-10-18 17:59       ` Tom Rini
2017-10-18 23:28         ` Andrew Turner
2017-10-18 23:53           ` Rob Herring
2017-10-19 14:00             ` Alexandre Torgue
2017-10-19 14:59               ` Rob Herring
2017-10-19 18:46                 ` Frank Rowand
2017-10-20  9:55                   ` Alexandre Torgue
2017-10-20 10:01                     ` David Gibson
2017-10-20 13:37                     ` Rob Herring
2017-10-22  8:25                       ` David Gibson
2017-10-20 13:47                 ` Alexandre Torgue
2017-10-19  0:04         ` Mark Brown
2017-10-19 11:10 ` Grant Likely
2017-10-24  7:37   ` Boris Brezillon
2017-10-25 14:40     ` Maxime Ripard
2017-10-26  5:47   ` Frank Rowand
2017-10-26  7:17   ` Grant Likely

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=7384dfc6-1068-eb6a-ae5f-7e805be8c48e@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=Julia.Lawall@lip6.fr \
    --cc=andy.gross@linaro.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=devicetree-spec@vger.kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --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