From: Grant Likely <grant.likely@secretlab.ca>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] Addressing Complex Dependencies - Tuesday 9:30am - Coronado/Devargas
Date: Tue, 1 Nov 2016 11:56:33 -0600 [thread overview]
Message-ID: <CACxGe6smZrw0STpHjzhSjybgW6bLrMKfyETO+-vuhHRT0yzWRQ@mail.gmail.com> (raw)
In-Reply-To: <CAB=NE6VBCC6SEzXTJi=HRSDbsCVXcw-1gwjXdgZzw+UGDn9j0A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
For those who want to brainstorm how to teach driver core about probe order
dependencies, we'll be meeting at 2:00 in "Milagro"
This will be a working session to try and come up with a design. If we make
any progress, we can do a readout later in the week for a larger audience
here at Plumbers.
Cheers,
g.
On Monday, 31 October 2016, Luis R. Rodriguez <mcgrof@kernel.org> wrote:
> 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
> _______________________________________________
> Ksummit-discuss mailing list
> Ksummit-discuss@lists.linuxfoundation.org <javascript:;>
> https://lists.linuxfoundation.org/mailman/listinfo/ksummit-discuss
>
[-- Attachment #2: Type: text/html, Size: 1711 bytes --]
next prev parent reply other threads:[~2016-11-01 17:56 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
2016-11-01 17:56 ` Grant Likely [this message]
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=CACxGe6smZrw0STpHjzhSjybgW6bLrMKfyETO+-vuhHRT0yzWRQ@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mcgrof@kernel.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