From: patchwork-bot+netdevbpf@kernel.org
To: Nathan Chancellor <nathan@kernel.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, vadim.fedorenko@linux.dev,
kory.maincent@bootlin.com, netdev@vger.kernel.org,
llvm@lists.linux.dev, patches@lists.linux.dev
Subject: Re: [PATCH net-next v2] net: netcp: ethss: Fix type of first parameter in hwtstamp stubs
Date: Wed, 12 Nov 2025 02:00:22 +0000 [thread overview]
Message-ID: <176291282249.3632748.2889753579213224698.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251110-netcp_ethss-fix-cpts-stubs-clang-wifpts-v2-1-aa6204ec1f43@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 10 Nov 2025 13:55:34 -0700 you wrote:
> When building without CONFIG_TI_CPTS, there are a series of errors from
> -Wincompatible-pointer-types:
>
> drivers/net/ethernet/ti/netcp_ethss.c:3831:27: error: initialization of 'int (*)(void *, struct kernel_hwtstamp_config *)' from incompatible pointer type 'int (*)(struct gbe_intf *, struct kernel_hwtstamp_config *)' [-Wincompatible-pointer-types]
> 3831 | .hwtstamp_get = gbe_hwtstamp_get,
> | ^~~~~~~~~~~~~~~~
> drivers/net/ethernet/ti/netcp_ethss.c:3831:27: note: (near initialization for 'gbe_module.hwtstamp_get')
> drivers/net/ethernet/ti/netcp_ethss.c:2758:19: note: 'gbe_hwtstamp_get' declared here
> 2758 | static inline int gbe_hwtstamp_get(struct gbe_intf *gbe_intf,
> | ^~~~~~~~~~~~~~~~
> drivers/net/ethernet/ti/netcp_ethss.c:3832:27: error: initialization of 'int (*)(void *, struct kernel_hwtstamp_config *, struct netlink_ext_ack *)' from incompatible pointer type 'int (*)(struct gbe_intf *, struct kernel_hwtstamp_config *, struct netlink_ext_ack *)' [-Wincompatible-pointer-types]
> 3832 | .hwtstamp_set = gbe_hwtstamp_set,
> | ^~~~~~~~~~~~~~~~
> drivers/net/ethernet/ti/netcp_ethss.c:3832:27: note: (near initialization for 'gbe_module.hwtstamp_set')
> drivers/net/ethernet/ti/netcp_ethss.c:2764:19: note: 'gbe_hwtstamp_set' declared here
> 2764 | static inline int gbe_hwtstamp_set(struct gbe_intf *gbe_intf,
> | ^~~~~~~~~~~~~~~~
>
> [...]
Here is the summary with links:
- [net-next,v2] net: netcp: ethss: Fix type of first parameter in hwtstamp stubs
https://git.kernel.org/netdev/net-next/c/34bff6f03c13
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-11-12 2:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 20:55 [PATCH net-next v2] net: netcp: ethss: Fix type of first parameter in hwtstamp stubs Nathan Chancellor
2025-11-12 2:00 ` patchwork-bot+netdevbpf [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=176291282249.3632748.2889753579213224698.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=justinstitt@google.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=pabeni@redhat.com \
--cc=patches@lists.linux.dev \
--cc=vadim.fedorenko@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 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).