From: patchwork-bot+netdevbpf@kernel.org
To: Nick Alcock <nick.alcock@oracle.com>
Cc: netdev@vger.kernel.org, mcgrof@kernel.org,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
hasegawa-hitomi@fujitsu.com, jk@codeconstruct.com.au,
matt@codeconstruct.com.au, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH] mctp: remove MODULE_LICENSE in non-modules
Date: Fri, 10 Mar 2023 07:11:04 +0000 [thread overview]
Message-ID: <167843226440.11704.9102499483871080842.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230308121230.5354-2-nick.alcock@oracle.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 8 Mar 2023 12:12:30 +0000 you wrote:
> Since commit 8b41fc4454e ("kbuild: create modules.builtin without
> Makefile.modbuiltin or tristate.conf"), MODULE_LICENSE declarations
> are used to identify modules. As a consequence, uses of the macro
> in non-modules will cause modprobe to misidentify their containing
> object file as a module when it is not (false positives), and modprobe
> might succeed rather than failing with a suitable error message.
>
> [...]
Here is the summary with links:
- mctp: remove MODULE_LICENSE in non-modules
https://git.kernel.org/netdev/net-next/c/14296c7d72ec
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2023-03-10 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 12:12 [PATCH] lib: packing: remove MODULE_LICENSE in non-modules Nick Alcock
2023-03-08 12:12 ` [PATCH] mctp: " Nick Alcock
2023-03-10 7:11 ` patchwork-bot+netdevbpf [this message]
2023-03-10 7:30 ` [PATCH] lib: packing: " patchwork-bot+netdevbpf
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=167843226440.11704.9102499483871080842.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=mcgrof@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nick.alcock@oracle.com \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).