From: sashiko-bot@kernel.org
To: "Selvamani Rajagopal" <Selvamani.Rajagopal@onsemi.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH net-next v9 04/11] net: ethernet: oa_tc6: Move constant definitions to header file
Date: Sat, 10 Oct 2026 17:12:28 +0000 [thread overview]
Message-ID: <sashiko-outbox-166764@kernel.org> (raw)
In-Reply-To: <20261009-s2500-mac-phy-support-v9-4-dcefe1d0bf0d@onsemi.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] oa_tc6: oa_tc6_std_def.h is not self-contained
--
commit dc8b82e8ffa11bb2c910dd9a4dd8439a0dd981ef
Author: Selvamani Rajagopal <Selvamani.Rajagopal@onsemi.com>
net: ethernet: oa_tc6: Move constant definitions to header file
To help other source files within the module share the constant definitions,
some of the definitions from oa_tc6.c are moved to a header file. This header
file is still private to OA TC6 framework.
> diff --git a/drivers/net/ethernet/oa_tc6/oa_tc6_std_def.h b/drivers/net/ethernet/oa_tc6/oa_tc6_std_def.h
> new file mode 100644
> index 0000000000000..403a9c22b5f14
> --- /dev/null
> +++ b/drivers/net/ethernet/oa_tc6/oa_tc6_std_def.h
> @@ -0,0 +1,125 @@
> +/* SPDX-License-Identifier: GPL-2.0+ */
[ ... ]
> +#include <linux/ptp_clock_kernel.h>
> +#include <linux/net_tstamp.h>
> +#include <linux/netdevice.h>
> +#include <linux/spi/spi.h>
> +#include <linux/skbuff.h>
> +#include <linux/sched.h>
> +#include <linux/wait.h>
> +#include <linux/phy.h>
> +
> +/* Control command header */
> +#define OA_TC6_CTRL_HEADER_DATA_NOT_CTRL BIT(31)
[Severity: Low]
Does this header need to include <linux/bits.h>?
It looks like the BIT and GENMASK macros are used here, but the required
header is not explicitly included.
[ ... ]
> +/* Internal structure for MAC-PHY drivers */
> +struct oa_tc6 {
[ ... ]
> + bool int_flag;
> + bool disable_traffic;
> + bool prot_ctrl;
> + enum oa_tc6_quirk_flag quirk_flags;
[Severity: Low]
Should this header also include <linux/oa_tc6.h>?
It appears the full definition of enum oa_tc6_quirk_flag is required here
to determine the size of struct oa_tc6.
Could this missing dependency cause compilation errors if other C files
include this header without first including <linux/oa_tc6.h>?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261009-s2500-mac-phy-support-v9-0-dcefe1d0bf0d@onsemi.com?part=4
next prev parent reply other threads:[~2026-10-10 17:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 17:12 [PATCH net-next v9 00/11] Support for onsemi's S2500 10Base-T1S MAC-PHY Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-09 17:12 ` [PATCH net-next v9 01/11] dt-bindings: net: add onsemi's S2500 Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-09 17:12 ` [PATCH net-next v9 02/11] Documentation: networking: Add timestamp related APIs to OA TC6 framework Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 03/11] net: ethernet: oa_tc6: Move oa_tc6.c to its own directory Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-09 18:40 ` Selvamani Rajagopal
2026-10-10 17:12 ` sashiko-bot
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 04/11] net: ethernet: oa_tc6: Move constant definitions to header file Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-10 17:12 ` sashiko-bot [this message]
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 05/11] net: ethernet: oa_tc6: Support for hardware timestamp Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-10 17:12 ` sashiko-bot
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 06/11] net: ethernet: oa_tc6: Support for vendor specific MMS Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-09 18:43 ` Selvamani Rajagopal
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 07/11] net: phy: ncn26000: Enable enhanced noise immunity Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 08/11] onsemi: s2500: Add driver support for S2500 MAC-PHY Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-09 23:02 ` Randy Dunlap
2026-10-10 17:12 ` sashiko-bot
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 09/11] onsemi: s2500: Added selftest support to onsemi's S2500 driver Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-10 17:12 ` sashiko-bot
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 10/11] net: phy: ncn26000: Support for onsemi's S2500 internal phy Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-10 17:12 ` sashiko-bot
2026-10-10 19:40 ` netdev-bot+sashiko
2026-10-09 17:12 ` [PATCH net-next v9 11/11] net: phy: ncn26000: Support for loopback Selvamani Rajagopal via B4 Relay
2026-10-09 17:12 ` Selvamani Rajagopal
2026-10-10 19:40 ` netdev-bot+sashiko
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=sashiko-outbox-166764@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Selvamani.Rajagopal@onsemi.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.