All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Vladimir Oltean <vladimir.oltean@nxp.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH net] net: mdio: don't defer probe forever if PHY IRQ provider is missing
Date: Thu, 7 Apr 2022 07:23:24 +0200	[thread overview]
Message-ID: <Yk51TIeGfFmfusQL@kroah.com> (raw)
In-Reply-To: <20220406172550.6408c990@kernel.org>

On Wed, Apr 06, 2022 at 05:25:50PM -0700, Jakub Kicinski wrote:
> On Wed, 6 Apr 2022 23:19:57 +0000 Vladimir Oltean wrote:
> > On Wed, Apr 06, 2022 at 03:34:43PM -0700, Jakub Kicinski wrote:
> > > > +	if (rc == -EPROBE_DEFER)
> > > > +		rc = driver_deferred_probe_check_state(&phy->mdio.dev);
> > > This one's not exported, allmodconfig build fails.  
> > 
> > Oops, I didn't realize that all its callers except for FWNODE_MDIO are built-in.
> > 
> > Do you prefer me exporting the symbol as part of the same patch or a different one?
> 
> I presume single patch is fine, but driver_deferred_probe_check_state()
> lives in Greg's realm, so let's add Greg in case he prefers a separate
> patch or more.

separate patch that I can NAK as I do not understand why this is needed
at all :)

thanks,

greg k-h

  reply	other threads:[~2022-04-07  5:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06 20:23 [PATCH net] net: mdio: don't defer probe forever if PHY IRQ provider is missing Vladimir Oltean
2022-04-06 22:34 ` Jakub Kicinski
2022-04-06 23:19   ` Vladimir Oltean
2022-04-07  0:25     ` Jakub Kicinski
2022-04-07  5:23       ` Greg Kroah-Hartman [this message]
2022-04-07  5:35         ` Jakub Kicinski
2022-04-07 17:04           ` Greg Kroah-Hartman

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=Yk51TIeGfFmfusQL@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=robin.murphy@arm.com \
    --cc=vladimir.oltean@nxp.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.