netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Qingtao Cao <qingtao.cao.au@gmail.com>
Cc: Qingtao Cao <qingtao.cao@digi.com>, Andrew Lunn <andrew@lunn.ch>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4 1/1] net: phy: marvell: make use of fiber autoneg bypass mode
Date: Fri, 4 Oct 2024 22:54:03 +0100	[thread overview]
Message-ID: <ZwBj-3t6S3SL9Fyu@shell.armlinux.org.uk> (raw)
In-Reply-To: <20241004212711.422811-1-qingtao.cao@digi.com>

On Sat, Oct 05, 2024 at 07:27:11AM +1000, Qingtao Cao wrote:
> 88E151x supports the SGMII autoneg bypass mode and it defaults to be
> enabled. When it is activated, the device assumes a link-up status so
> avoid bringing down fibre link in this case

Please can you stop posting new patches while there is still discussion
going on.

I'm simply going to NAK this patch, because you haven't given any time
for discussion to conclude on your previous offering, and I see no
point in even bothering to read this while the whole subject of
whether AN bypass should be used is still unsettled.

Please wait for discussion to conclude before posting new patches.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!

  reply	other threads:[~2024-10-04 21:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 21:27 [PATCH net-next v4 1/1] net: phy: marvell: make use of fiber autoneg bypass mode Qingtao Cao
2024-10-04 21:54 ` Russell King (Oracle) [this message]
2024-10-05 16:43   ` Andrew Lunn

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=ZwBj-3t6S3SL9Fyu@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=qingtao.cao.au@gmail.com \
    --cc=qingtao.cao@digi.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).