From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 33B26C4320A for ; Thu, 2 Sep 2021 10:37:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F139C60FC0 for ; Thu, 2 Sep 2021 10:37:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S244285AbhIBKih (ORCPT ); Thu, 2 Sep 2021 06:38:37 -0400 Received: from mail.kernel.org ([198.145.29.99]:59446 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233714AbhIBKig (ORCPT ); Thu, 2 Sep 2021 06:38:36 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id DF24660FC0; Thu, 2 Sep 2021 10:37:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1630579057; bh=myvl5C6bWm7U0pzspU+p4yxBN99ESzBLn2YM1d94xhI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Y1yzDS+opMJgUTIiJtfY1tYRDR+ZoWRoM/XEVw8SmpFek+7lRlcxUoUWGno6E7mdj cYzjWp98uMwc4FoQWi0f3X/b4zLs4z3W5tN88P1FmQX58NJbyRZ05IQkoRGnnhXN1T aAqy72exzeNO9ymO3tU3JSEbDQWSMFm4jNa2J6XQ= Date: Thu, 2 Sep 2021 12:37:34 +0200 From: Greg Kroah-Hartman To: Vladimir Oltean Cc: Vladimir Oltean , netdev@vger.kernel.org, "Rafael J. Wysocki" , Andrew Lunn , Heiner Kallweit , Russell King , "David S. Miller" , Jakub Kicinski , Vivien Didelot , Florian Fainelli , linux-kernel@vger.kernel.org, Linus Walleij , Alvin =?utf-8?Q?=C5=A0ipraga?= , ACPI Devel Maling List , kernel-team , Len Brown Subject: Re: [RFC PATCH net-next 1/3] net: phy: don't bind genphy in phy_attach_direct if the specific driver defers probe Message-ID: References: <20210901225053.1205571-1-vladimir.oltean@nxp.com> <20210901225053.1205571-2-vladimir.oltean@nxp.com> <20210902101150.dnd2gycc7ekjwgc6@skbuf> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210902101150.dnd2gycc7ekjwgc6@skbuf> Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Thu, Sep 02, 2021 at 01:11:50PM +0300, Vladimir Oltean wrote: > On Thu, Sep 02, 2021 at 07:43:10AM +0200, Greg Kroah-Hartman wrote: > > Wait, no, this should not be a "special" thing, and why would the list > > of deferred probe show this? > > Why as in why would it work/do what I want, or as in why would you want to do that? Both! :) > > If a bus wants to have this type of "generic vs. specific" logic, then > > it needs to handle it in the bus logic itself as that does NOT fit into > > the normal driver model at all. Don't try to get a "hint" of this by > > messing with the probe function list. > > Where and how? Do you have an example? No I do not, sorry, most busses do not do this for obvious ordering / loading / we are not that crazy reasons. What is causing this all to suddenly break? The devlink stuff? thanks, greg k-h