netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Xu Liang <lxu@maxlinear.com>
Cc: <andrew@lunn.ch>, <hkallweit1@gmail.com>,
	<netdev@vger.kernel.org>, <davem@davemloft.net>,
	<linux@armlinux.org.uk>, <hmehrtens@maxlinear.com>,
	<tmohren@maxlinear.com>, <mohammad.athari.ismail@intel.com>,
	<edumazet@google.com>, <michael@walle.cc>, <pabeni@redhat.com>
Subject: Re: [PATCH net-next v3] net: phy: mxl-gpy: fix delay time required by loopback disable function
Date: Thu, 12 Jan 2023 21:30:34 -0800	[thread overview]
Message-ID: <20230112213034.074ff77e@kernel.org> (raw)
In-Reply-To: <20230111082201.15181-1-lxu@maxlinear.com>

On Wed, 11 Jan 2023 16:22:01 +0800 Xu Liang wrote:
> GPY2xx devices need 3 seconds to fully switch out of loopback mode
> before it can safely re-enter loopback mode.
> 
> Signed-off-by: Xu Liang <lxu@maxlinear.com>

Looks like a fix, it needs a Fixes tag and needs to go to net.

Michael already asked you for the Fixes tag on v2, why did you decide
to switch to net-next instead?

We don't route fixes to net-next when they are targeting less
important features, in case that's your reason. Either something 
is a fix or it's not. If you think this is not a fix - you need to
explain in the commit message why.

      parent reply	other threads:[~2023-01-13  5:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  8:22 [PATCH net-next v3] net: phy: mxl-gpy: fix delay time required by loopback disable function Xu Liang
2023-01-11 13:40 ` Andrew Lunn
2023-01-13  5:30 ` Jakub Kicinski [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=20230112213034.074ff77e@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=hmehrtens@maxlinear.com \
    --cc=linux@armlinux.org.uk \
    --cc=lxu@maxlinear.com \
    --cc=michael@walle.cc \
    --cc=mohammad.athari.ismail@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=tmohren@maxlinear.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).