From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Addressing Complex Dependencies - Tuesday 9:30am - Coronado/Devargas
Date: Mon, 31 Oct 2016 15:00:22 -0700 [thread overview]
Message-ID: <CAB=NE6VBCC6SEzXTJi=HRSDbsCVXcw-1gwjXdgZzw+UGDn9j0A@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6Wo-mWdJF8k9yGcsORatpNtiiug+jXdGP60xhd0F+jydg@mail.gmail.com>
Update:
We've reduced the topics that will be covered and time that will be
required as follows:
The shared topics with the Audio workshop will take place first at
9:30am-10:30am at Sweeney CDE:
* Device hierarchy (just not a tree but a graph)
* Handling cycles on the graph proposals
Then we move to Coronado room 10:30am-12:30pm for:
* Functional dependencies (now merged on Greg's tree)
* Resource tracking / allocation framework
* Media controller feature graph
* Linker tables
* Async probe
Luis
next prev parent reply other threads:[~2016-10-31 22:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 18:35 Luis R. Rodriguez
2016-10-31 19:32 ` James Bottomley
2016-10-31 22:00 ` Luis R. Rodriguez [this message]
2016-11-01 17:56 ` Grant Likely
2016-11-02 3:48 ` Rafael J. Wysocki
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='CAB=NE6VBCC6SEzXTJi=HRSDbsCVXcw-1gwjXdgZzw+UGDn9j0A@mail.gmail.com' \
--to=mcgrof@kernel.org \
--cc=ksummit-discuss@lists.linuxfoundation.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