From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Furong Xu <0x1207@gmail.com>
Cc: netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
xfr@outlook.com
Subject: Re: [PATCH net-next v1] net: stmmac: Move extern declarations from common.h to hwif.h
Date: Sat, 7 Dec 2024 10:13:14 +0000 [thread overview]
Message-ID: <Z1QfupFfg07jTMUc@shell.armlinux.org.uk> (raw)
In-Reply-To: <20241207070248.4049877-1-0x1207@gmail.com>
On Sat, Dec 07, 2024 at 03:02:48PM +0800, Furong Xu wrote:
> These extern declarations are referenced in hwif.c only.
> Move them to hwif.h just like the other extern declarations.
We normally have declarations in a header file that corresponds to their
definition, rather than where they are used.
> Compile tested only.
> No functional change intended.
>
> Signed-off-by: Furong Xu <0x1207@gmail.com>
> ---
> drivers/net/ethernet/stmicro/stmmac/common.h | 14 --------------
> drivers/net/ethernet/stmicro/stmmac/hwif.h | 14 ++++++++++++++
> 2 files changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/common.h b/drivers/net/ethernet/stmicro/stmmac/common.h
> index 1367fa5c9b8e..fbcf07d201cf 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/common.h
> +++ b/drivers/net/ethernet/stmicro/stmmac/common.h
> @@ -543,18 +543,8 @@ struct dma_features {
> #define STMMAC_VLAN_INSERT 0x2
> #define STMMAC_VLAN_REPLACE 0x3
>
> -extern const struct stmmac_desc_ops enh_desc_ops;
Defined in enh_desc.c, but no header for it, so either common.h or
hwif.h seems sensible.
> -extern const struct stmmac_desc_ops ndesc_ops;
Defined in norm_desc.c, same situation as previous one.
> -
> struct mac_device_info;
>
> -extern const struct stmmac_hwtimestamp stmmac_ptp;
Defined in stmmac_hwtstamp.c, same as above.
> -extern const struct stmmac_hwtimestamp dwmac1000_ptp;
Ditto.
> -extern const struct stmmac_mode_ops dwmac4_ring_mode_ops;
Defined in dwmac4_descs.c, maybe dwmac4_descs.h or dwmac4.h would make
more sense than hwif.c ?
> -
> -extern const struct ptp_clock_info stmmac_ptp_clock_ops;
Defined in stmmac_ptp.c, and there is stmmac_ptp.h which contains a
number of function declarations, so maybe moving that there would
make more sense?
> -extern const struct ptp_clock_info dwmac1000_ptp_clock_ops;
Same as stmmac_ptp_clock_ops.
> -
> struct mac_link {
> u32 caps;
> u32 speed_mask;
> @@ -641,8 +631,4 @@ void stmmac_dwmac4_set_mac(void __iomem *ioaddr, bool enable);
>
> void dwmac_dma_flush_tx_fifo(void __iomem *ioaddr);
>
> -extern const struct stmmac_mode_ops ring_mode_ops;
Defined in ring_mode.c, same as enh_desc_ops.
> -extern const struct stmmac_mode_ops chain_mode_ops;
Defined in chain_mode.c, same as enh_desc_ops.
> -extern const struct stmmac_desc_ops dwmac4_desc_ops;
Defined in dwmac4_descs.c, similar situation to dwmac4_ring_mode_ops
above.
So I think rather than bulk moving these to hwif.h, where some of them
remain out of place, maybe placing some in a more appropriate header
would be better.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 80Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2024-12-07 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-07 7:02 [PATCH net-next v1] net: stmmac: Move extern declarations from common.h to hwif.h Furong Xu
2024-12-07 10:13 ` Russell King (Oracle) [this message]
2024-12-07 10:39 ` Furong Xu
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=Z1QfupFfg07jTMUc@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=0x1207@gmail.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=xfr@outlook.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).