From: Florian Fainelli <f.fainelli@gmail.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>, netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>, "Andrew Lunn" <andrew@lunn.ch>,
"Luiz Angelo Daros de Luca" <luizluca@gmail.com>,
"Alvin Šipraga" <alsi@bang-olufsen.dk>,
"Madhuri Sripada" <madhuri.sripada@microchip.com>,
"Marcin Wojtas" <mw@semihalf.com>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Tobias Waldekranz" <tobias@waldekranz.com>,
"Arun Ramadoss" <arun.ramadoss@microchip.com>,
"Russell King (Oracle)" <rmk+kernel@armlinux.org.uk>,
"Jonathan Corbet" <corbet@lwn.net>
Subject: Re: [PATCH net 2/4] docs: net: dsa: update platform_data documentation
Date: Fri, 8 Dec 2023 14:33:49 -0800 [thread overview]
Message-ID: <ed1911a6-f7ab-49fd-a198-d1cfca77f7a0@gmail.com> (raw)
In-Reply-To: <20231208193518.2018114-3-vladimir.oltean@nxp.com>
On 12/8/23 11:35, Vladimir Oltean wrote:
> We were documenting a bunch of stuff which was removed in commit
> 93e86b3bc842 ("net: dsa: Remove legacy probing support"). There's some
> further cleanup to do in struct dsa_chip_data, so rather than describing
> every possible field (when maybe we should be switching to kerneldoc
> format), just say what's important about it.
>
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
--
Florian
next prev parent reply other threads:[~2023-12-08 22:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 19:35 [PATCH net 0/4] Add some history to the DSA documentation Vladimir Oltean
2023-12-08 19:35 ` [PATCH net 1/4] docs: net: dsa: document the tagger-owned storage mechanism Vladimir Oltean
2023-12-08 22:15 ` Linus Walleij
2023-12-08 22:32 ` Florian Fainelli
2023-12-10 13:37 ` Alvin Šipraga
2023-12-08 19:35 ` [PATCH net 2/4] docs: net: dsa: update platform_data documentation Vladimir Oltean
2023-12-08 22:19 ` Linus Walleij
2023-12-09 0:52 ` Vladimir Oltean
2023-12-08 22:33 ` Florian Fainelli [this message]
2023-12-10 13:37 ` Alvin Šipraga
2023-12-08 19:35 ` [PATCH net 3/4] docs: net: dsa: update user MDIO bus documentation Vladimir Oltean
2023-12-08 22:22 ` Linus Walleij
2023-12-08 22:36 ` Florian Fainelli
2023-12-09 1:22 ` Vladimir Oltean
2023-12-09 21:49 ` Linus Walleij
2023-12-10 13:48 ` Alvin Šipraga
2023-12-11 14:35 ` Vladimir Oltean
2023-12-13 5:30 ` Luiz Angelo Daros de Luca
2023-12-13 12:06 ` Vladimir Oltean
2023-12-08 19:35 ` [PATCH net 4/4] docs: net: dsa: replace TODO section with info about history and devel ideas Vladimir Oltean
2023-12-08 22:40 ` Linus Walleij
2023-12-08 23:03 ` Florian Fainelli
2023-12-09 1:58 ` Vladimir Oltean
2023-12-11 17:29 ` Florian Fainelli
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=ed1911a6-f7ab-49fd-a198-d1cfca77f7a0@gmail.com \
--to=f.fainelli@gmail.com \
--cc=alsi@bang-olufsen.dk \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=luizluca@gmail.com \
--cc=madhuri.sripada@microchip.com \
--cc=mw@semihalf.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
--cc=tobias@waldekranz.com \
--cc=vladimir.oltean@nxp.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