Re: [Ksummit-discuss] [TECH TOPIC] Addressing complex dependencies and semantics (v2)

[Greg KH <greg@kroah.com>]

On Thu, Jul 28, 2016 at 11:49:49PM +0200, Lars-Peter Clausen wrote:
> On 07/27/2016 07:58 PM, Luis R. Rodriguez wrote:
> > On Wed, Jul 27, 2016 at 06:26:36PM +0100, Mark Brown wrote:
> >>> to help enable asynchronous probe, however for built-in devices this requires
> >>> very specific platform knowledge otherwise using async probe will blow up
> >>> your kernel -- if you get it right though, using async probe can help with
> >>
> >> I'm not sure what specific platform knowledge you're thinking of here?
> >> We have coverage for most things in the form of deferred probe (messy
> >> though it is).
> > 
> > Deferred probe is a complete a hack and sub-optimal.

It's the best hack that people have come up with to solve the problem so
far.

> I fully agree. In the past though there were a few good attempts of
> providing something better than probe deferral, but those were always
> quickly shutdown by GregKH for failing to prove that probe deferral
> really is insufficient.
> 
> This probably an issue of presentation, but for future attempts it
> should be kept in mind that hard numbers on why this is better greatly
> improve the chance of it being accepted.

If you don't have such numbers, why should I ever accept any changes?
You need to show a benefit of code, otherwise you are just pointless
churning things for no reason.

And also, don't try presenting patches that force every driver or
subsystem to be changed for no good reason, that's one reason I have
shot down patches in this area as well.

good luck!

greg k-h