From: patchwork-bot+netdevbpf@kernel.org
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Jose.Abreu@synopsys.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] net: dwc-xlgmac: fix missing MODULE_DESCRIPTION() warning
Date: Tue, 18 Jun 2024 01:10:29 +0000 [thread overview]
Message-ID: <171867302991.10892.6137229238136764379.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240616-md-hexagon-drivers-net-ethernet-synopsys-v1-1-55852b60aef8@quicinc.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 16 Jun 2024 13:01:48 -0700 you wrote:
> With ARCH=hexagon, make allmodconfig && make W=1 C=1 reports:
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/net/ethernet/synopsys/dwc-xlgmac.o
>
> With most other ARCH settings the MODULE_DESCRIPTION() is provided by
> the macro invocation in dwc-xlgmac-pci.c. However, for hexagon, the
> PCI bus is not enabled, and hence CONFIG_DWC_XLGMAC_PCI is not set.
> As a result, dwc-xlgmac-pci.c is not compiled, and hence is not linked
> into dwc-xlgmac.o.
>
> [...]
Here is the summary with links:
- net: dwc-xlgmac: fix missing MODULE_DESCRIPTION() warning
https://git.kernel.org/netdev/net-next/c/0d9bb144276e
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:[~2024-06-18 1:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 20:01 [PATCH] net: dwc-xlgmac: fix missing MODULE_DESCRIPTION() warning Jeff Johnson
2024-06-17 11:04 ` Jiri Pirko
2024-06-18 0:14 ` Jakub Kicinski
2024-06-20 23:41 ` Jeff Johnson
2024-06-21 2:03 ` Jakub Kicinski
2024-06-18 1: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=171867302991.10892.6137229238136764379.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Jose.Abreu@synopsys.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_jjohnson@quicinc.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