mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Qingtao Cao <qingtao.cao.au@gmail.com>,
	Qingtao Cao <qingtao.cao@digi.com>,
	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: Sat, 5 Oct 2024 18:43:41 +0200	[thread overview]
Message-ID: <e68c2806-8058-4669-8f47-726ddb60c90a@lunn.ch> (raw)
In-Reply-To: <ZwBj-3t6S3SL9Fyu@shell.armlinux.org.uk>

On Fri, Oct 04, 2024 at 10:54:03PM +0100, Russell King (Oracle) wrote:
> 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.

+1


    Andrew

---
pw-bot: cr

      reply	other threads:[~2024-10-05 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 21:27 Qingtao Cao
2024-10-04 21:54 ` Russell King (Oracle)
2024-10-05 16:43   ` Andrew Lunn [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=e68c2806-8058-4669-8f47-726ddb60c90a@lunn.ch \
    --to=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=linux@armlinux.org.uk \
    --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

all inboxes | Powered by JetHome®