From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] Addressing Complex Dependencies - Tuesday 9:30am - Coronado/Devargas
Date: Wed, 02 Nov 2016 04:48:06 +0100 [thread overview]
Message-ID: <2057225.YvLP48r0ZV@vostro.rjw.lan> (raw)
In-Reply-To: <CACxGe6smZrw0STpHjzhSjybgW6bLrMKfyETO+-vuhHRT0yzWRQ@mail.gmail.com>
On Tuesday, November 01, 2016 11:56:33 AM Grant Likely wrote:
> 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.
For everyone interested, the series of "device dependencies tracking" patches
mentioned during the discussion today is available from a git branch at
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git device-links-test
Thanks,
Rafael
> 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
prev parent reply other threads:[~2016-11-02 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 18:35 [Ksummit-discuss] Addressing Complex Dependencies - Tuesday 9:30am - Coronado/Devargas 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
2016-11-02 3:48 ` Rafael J. Wysocki [this message]
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=2057225.YvLP48r0ZV@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).