From: Maxim Kochetkov <fido_max@inbox.ru>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
vivien.didelot@gmail.com, claudiu.manoil@nxp.com,
f.fainelli@gmail.com, netdev@vger.kernel.org
Subject: Re: 88E6176 dsa switch on ls1021a (GIANFAR)
Date: Mon, 13 Jul 2020 14:52:03 +0300 [thread overview]
Message-ID: <aa7fcc92-691a-0aad-c77e-f1a9a10f3468@inbox.ru> (raw)
In-Reply-To: <20200713112040.zn4fmuuttwqier5j@skbuf>
Sorry that was my mistake. That was my own custom patch for bridge (for
some old board).
Thank you very much!
13.07.2020 14:20, Vladimir Oltean wrote:
> This call path is interesting. How does br_fdb_update() end up calling
> dsa_legacy_fdb_add(), which is only accessible through .ndo_fdb_add? The
> only call path I see in the mainline kernel for .ndo_fdb_add() is from
> rtnl_fdb_add(), which seems to not be called here.
prev parent reply other threads:[~2020-07-13 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 9:54 88E6176 dsa switch on ls1021a (GIANFAR) Maxim Kochetkov
2020-07-13 11:20 ` Vladimir Oltean
2020-07-13 11:52 ` Maxim Kochetkov [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=aa7fcc92-691a-0aad-c77e-f1a9a10f3468@inbox.ru \
--to=fido_max@inbox.ru \
--cc=andrew@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vivien.didelot@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;
as well as URLs for NNTP newsgroup(s).