netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: "A. Sverdlin" <alexander.sverdlin@siemens.com>
Cc: netdev@vger.kernel.org, Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>
Subject: Re: [PATCH] net: dsa: lan9303: imply SMSC_PHY
Date: Wed, 15 May 2024 11:00:54 +0100	[thread overview]
Message-ID: <20240515100054.GC154012@kernel.org> (raw)
In-Reply-To: <20240514122605.662767-1-alexander.sverdlin@siemens.com>

On Tue, May 14, 2024 at 02:26:03PM +0200, A. Sverdlin wrote:
> From: Alexander Sverdlin <alexander.sverdlin@siemens.com>
> 
> Both LAN9303 and LAN9354 have internal PHYs on both external ports.
> Therefore a configuration without SMSC PHY support is non-practical at
> least and leads to:
> 
> LAN9303_MDIO 8000f00.mdio:00: Found LAN9303 rev. 1
> mdio_bus 8000f00.mdio:00: deferred probe pending: (reason unknown)
> 
> Signed-off-by: Alexander Sverdlin <alexander.sverdlin@siemens.com>

Hi Alexander,

Thanks for your patch.

As an enhancement - as opposed to a fix - this patch should be
targeted at the net-next kernel. And it's best to explicitly note that
in the subject.

	Subject: [PATCH net-next] ...

As it happens, net-next is currently closed for the v6.10 merge window.
Please consider reposting as a PATCH once net-next re-opens, after 27th May.

In the meantime, feel free to post new versions as you get feedback,
but please switch to posting as RFC during that time.

Link: https://docs.kernel.org/process/maintainer-netdev.html

-- 
pw-bot: defer

      reply	other threads:[~2024-05-15 10:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 12:26 [PATCH] net: dsa: lan9303: imply SMSC_PHY A. Sverdlin
2024-05-15 10:00 ` Simon Horman [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=20240515100054.GC154012@kernel.org \
    --to=horms@kernel.org \
    --cc=alexander.sverdlin@siemens.com \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.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 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 NNTP newsgroup(s).