mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Pawel Dembicki <paweldembicki@gmail.com>
Cc: netdev@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King <linux@armlinux.org.uk>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net 1/6] net: dsa: vsc73xx: fix port MAC configuration in full duplex mode
Date: Sat, 3 Aug 2024 01:12:36 +0200	[thread overview]
Message-ID: <fde76183-ba7d-41e9-bde7-9d717ad4c456@lunn.ch> (raw)
In-Reply-To: <20240802080403.739509-2-paweldembicki@gmail.com>

On Fri, Aug 02, 2024 at 10:03:58AM +0200, Pawel Dembicki wrote:
> According to the datasheet description ("Port Mode Procedure" in 5.6.2),
> the VSC73XX_MAC_CFG_WEXC_DIS bit is configured only for half duplex mode.
> 
> The WEXC_DIS bit is responsible for MAC behavior after an excessive
> collision. Let's set it as described in the datasheet.
> 
> Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com>
> ---
> This patch came from net-next series[0].
> Changes since net-next:
>   - rebased to netdev/main only

Since this is targeting net, a fixes tag would still be good. If
nothing else it prevents somebody trying to backport it to linux
2.6.39 :-)

       Andrew

  parent reply	other threads:[~2024-08-02 23:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  8:03 [PATCH net 0/6] net: dsa: vsc73xx: fix MDIO bus access and PHY operations Pawel Dembicki
2024-08-02  8:03 ` [PATCH net 1/6] net: dsa: vsc73xx: fix port MAC configuration in full duplex mode Pawel Dembicki
2024-08-02 20:58   ` Linus Walleij
2024-08-02 21:54   ` Florian Fainelli
2024-08-02 23:12   ` Andrew Lunn [this message]
2024-08-02  8:03 ` [PATCH net 2/6] net: dsa: vsc73xx: pass value in phy_write operation Pawel Dembicki
2024-08-02 20:59   ` Linus Walleij
2024-08-02 21:02   ` Linus Walleij
2024-08-02 21:53   ` Florian Fainelli
2024-08-02  8:04 ` [PATCH net 3/6] net: dsa: vsc73xx: use defined values in phy operations Pawel Dembicki
2024-08-02 21:03   ` Linus Walleij
2024-08-02 21:57   ` Florian Fainelli
2024-08-02 22:15   ` Vladimir Oltean
2024-08-04 23:08     ` Paweł Dembicki
2024-08-02  8:04 ` [PATCH net 4/6] net: dsa: vsc73xx: check busy flag in MDIO operations Pawel Dembicki
2024-08-02 21:04   ` Linus Walleij
2024-08-02 21:54   ` Florian Fainelli
2024-08-02  8:04 ` [PATCH net 5/6] net: dsa: vsc73xx: allow phy resetting Pawel Dembicki
2024-08-02 13:01   ` Russell King (Oracle)
2024-08-02 21:07   ` Linus Walleij
2024-08-02 21:55   ` Florian Fainelli
2024-08-02  8:04 ` [PATCH net 6/6] net: phy: vitesse: repair vsc73xx autonegotiation Pawel Dembicki
2024-08-02 13:03   ` Russell King (Oracle)
2024-08-02 20:40     ` Paweł Dembicki
2024-08-02 21:08   ` Linus Walleij

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=fde76183-ba7d-41e9-bde7-9d717ad4c456@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=paweldembicki@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

all inboxes | Powered by JetHome®