mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <Arun.Ramadoss@microchip.com>
To: <andrew@lunn.ch>, <olteanv@gmail.com>, <davem@davemloft.net>,
	<linux@armlinux.org.uk>, <conor+dt@kernel.org>,
	<Woojung.Huh@microchip.com>, <robh@kernel.org>,
	<krzk+dt@kernel.org>, <f.fainelli@gmail.com>, <kuba@kernel.org>,
	<vtpieter@gmail.com>, <UNGLinuxDriver@microchip.com>,
	<marex@denx.de>, <edumazet@google.com>, <pabeni@redhat.com>
Cc: <pieter.van.trappen@cern.ch>, <devicetree@vger.kernel.org>,
	<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v5 5/6] net: dsa: microchip: fix KSZ87xx family structure wrt the datasheet
Date: Tue, 13 Aug 2024 03:16:27 +0000	[thread overview]
Message-ID: <1b0f215df4b8cd008e07e682ee9de191b245e186.camel@microchip.com> (raw)
In-Reply-To: <20240812153015.653044-6-vtpieter@gmail.com>

On Mon, 2024-08-12 at 17:29 +0200, vtpieter@gmail.com wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> From: Pieter Van Trappen <pieter.van.trappen@cern.ch>
> 
> The KSZ87xx switches have 32 static MAC address table entries and not
> 8. This fixes -ENOSPC non-critical errors from ksz8_add_sta_mac when
> configured as a bridge.
> 
> Add a new ksz87xx_dev_ops structure to be able to use the
> ksz_r_mib_stat64 pointer for this family; this corrects a wrong
> mib->counters cast to ksz88xx_stats_raw. This fixes iproute2
> statistics. Rename ksz8_dev_ops structure to ksz88x3_dev_ops, in line
> with ksz_is_* naming conventions from ksz_common.h.
> 
> Signed-off-by: Pieter Van Trappen <pieter.van.trappen@cern.ch>

Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com>


  reply	other threads:[~2024-08-13  3:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-12 15:29 [PATCH net-next v5 0/6] net: dsa: microchip: ksz8795: add Wake on LAN support vtpieter
2024-08-12 15:29 ` [PATCH net-next v5 1/6] dt-bindings: net: dsa: microchip: add microchip,pme-active-high flag vtpieter
2024-08-12 15:29 ` [PATCH net-next v5 2/6] net: dsa: microchip: move KSZ9477 WoL functions to ksz_common vtpieter
2024-08-12 15:29 ` [PATCH net-next v5 3/6] net: dsa: microchip: generalize KSZ9477 WoL functions at ksz_common vtpieter
2024-08-12 15:29 ` [PATCH net-next v5 4/6] net: dsa: microchip: add WoL support for KSZ87xx family vtpieter
2024-08-12 15:29 ` [PATCH net-next v5 5/6] net: dsa: microchip: fix KSZ87xx family structure wrt the datasheet vtpieter
2024-08-13  3:16   ` Arun.Ramadoss [this message]
2024-08-12 15:29 ` [PATCH net-next v5 6/6] net: dsa: microchip: fix tag_ksz egress mask for KSZ8795 family vtpieter
2024-08-13  3:28   ` Arun.Ramadoss

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=1b0f215df4b8cd008e07e682ee9de191b245e186.camel@microchip.com \
    --to=arun.ramadoss@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=marex@denx.de \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=pieter.van.trappen@cern.ch \
    --cc=robh@kernel.org \
    --cc=vtpieter@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®