From: patchwork-bot+netdevbpf@kernel.org
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
richardcochran@gmail.com, davem@davemloft.net, arnd@arndb.de,
lkp@intel.com
Subject: Re: [PATCH net-next] net: lan966x: Fix compilation error
Date: Sat, 30 Apr 2022 14:30:12 +0000 [thread overview]
Message-ID: <165132901295.11133.16561971820560838963.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220429071953.4079517-1-horatiu.vultur@microchip.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 29 Apr 2022 09:19:53 +0200 you wrote:
> Starting from the blamed commit, the lan966x build fails with the
> following compilation error:
>
> drivers/net/ethernet/microchip/lan966x/lan966x_ptp.c:342:9: error: implicit declaration of function ‘ptp_find_pin_unlocked’ [-Werror=implicit-function-declaration]
> 342 | pin = ptp_find_pin_unlocked(phc->clock, PTP_PF_EXTTS, 0);
>
> The issue is that there is no stub function for ptp_find_pin_unlocked
> in case CONFIG_PTP_1588_CLOCK is not selected. Therefore add one.
>
> [...]
Here is the summary with links:
- [net-next] net: lan966x: Fix compilation error
https://git.kernel.org/netdev/net-next/c/48cec73a891c
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:[~2022-04-30 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 7:19 [PATCH net-next] net: lan966x: Fix compilation error Horatiu Vultur
2022-04-30 14:30 ` 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=165132901295.11133.16561971820560838963.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=horatiu.vultur@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@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