From: patchwork-bot+netdevbpf@kernel.org
To: Randy Dunlap <rdunlap@infradead.org>
Cc: netdev@vger.kernel.org, lkp@intel.com, olek2@wp.pl,
hauke@hauke-m.de, davem@davemloft.net, kuba@kernel.org,
john@phrozen.org, linux-mips@vger.kernel.org,
ralf@linux-mips.org, michael.opdenacker@bootlin.com
Subject: Re: [PATCH -net] net: ethernet: lantiq_etop: fix build errors/warnings
Date: Mon, 15 Nov 2021 14:10:08 +0000 [thread overview]
Message-ID: <163698540863.13805.40510360412441123.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211115010229.15933-1-rdunlap@infradead.org>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Sun, 14 Nov 2021 17:02:29 -0800 you wrote:
> Fix build error and warnings reported by kernel test robot:
>
> drivers/net/ethernet/lantiq_etop.c: In function 'ltq_etop_probe':
> drivers/net/ethernet/lantiq_etop.c:673:15: error: implicit declaration of function 'device_property_read_u32' [-Werror=implicit-function-declaration]
> 673 | err = device_property_read_u32(&pdev->dev, "lantiq,tx-burst-length", &priv->tx_burst_len);
>
> drivers/net/ethernet/lantiq_etop.c: At top level:
> drivers/net/ethernet/lantiq_etop.c:730:1: warning: no previous prototype for 'init_ltq_etop' [-Wmissing-prototypes]
> 730 | init_ltq_etop(void)
>
> [...]
Here is the summary with links:
- [-net] net: ethernet: lantiq_etop: fix build errors/warnings
https://git.kernel.org/netdev/net/c/e97b21e94652
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:[~2021-11-15 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 1:02 [PATCH -net] net: ethernet: lantiq_etop: fix build errors/warnings Randy Dunlap
2021-11-15 14:10 ` 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=163698540863.13805.40510360412441123.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lkp@intel.com \
--cc=michael.opdenacker@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olek2@wp.pl \
--cc=ralf@linux-mips.org \
--cc=rdunlap@infradead.org \
/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).