From: Andrew Lunn <andrew@lunn.ch>
To: David Yang <mmyangfl@gmail.com>
Cc: netdev@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2 1/2] net: dsa: motorcomm: Report error when FDB fails to add
Date: Tue, 10 Nov 2026 14:28:19 +0100 [thread overview]
Message-ID: <4f5b92b6-7dfc-4065-90bb-3f5398b0f2a0@lunn.ch> (raw)
In-Reply-To: <20261108094512.1285796-2-mmyangfl@gmail.com>
On Sun, Nov 08, 2026 at 05:45:09PM +0800, David Yang wrote:
> fdb_add() ignored any errors returned by the hardware. Return error for
> that case.
>
> In practice the 4096-entry table is hardly ever filled, and since
> fdb_add() will automatically expel dynamic entries, something bad will
> definitively happen before you fill it up with static entries. This,
> however, is in preparation for the upcoming static entry counters.
>
> Signed-off-by: David Yang <mmyangfl@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2026-11-10 13:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 9:45 [PATCH net-next v2 0/2] net: dsa: motorcomm: Add devlink info and resources David Yang
2026-11-08 9:45 ` [PATCH net-next v2 1/2] net: dsa: motorcomm: Report error when FDB fails to add David Yang
2026-11-09 9:46 ` netdev-bot+sashiko
2026-11-10 13:28 ` Andrew Lunn [this message]
2026-11-08 9:45 ` [PATCH net-next v2 2/2] net: dsa: motorcomm: Add devlink info and resources David Yang
2026-11-09 9:46 ` netdev-bot+sashiko
2026-11-10 13:32 ` 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=4f5b92b6-7dfc-4065-90bb-3f5398b0f2a0@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmyangfl@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.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®