[Ksummit-discuss] Deferred probing

[Mark Brown <broonie@kernel.org>]

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

On Mon, Oct 26, 2015 at 08:59:50PM -0400, tytso wrote:

> I didn't see that message, sorry.  I found it after spending many
> minutes searching an overflowing inbox, but it's not something which
> is scalable.

Please provide clearer information on the process that you are expecting
people to follow :(

> If you have specific requests, please use a separate subject line (so
> people who are massively behind on their e-mail during the conference
> have some *hope* of finding messages with real-time requests), and

I was hoping that replying to your message asking for new topics and
sending to the (different to normal) e-mail address you were requesting
was a good way of indicating a new topic.

> please don't reference "subject XXX on the lists" and expect folks to
> have to read a largish thread and to try to figure out what issues you
> want to talk about.

> Please send a 2-3 sentence summary of the issues you want to discuss
> --- I'm not sure I understand what needs to be discussed about
> "deferred probing and general device ordering" this week.

Currently we don't do anything useful to capture inter-device
dependencies outside the parent/child relationship.  This means that
during boot we can get a very largee number of probe attempts which gets
messy from a logging point of view and means that during suspend and
resume we don't do anything to make sure we're suspending and resuming
things in a useful order.

Currently it's all hacked with link order and is very fragile.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]