From: Thierry Reding <thierry.reding@gmail.com>
To: Nick Alcock <nick.alcock@oracle.com>, mcgrof@kernel.org
Cc: Hitomi Hasegawa <hasegawa-hitomi@fujitsu.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
linux-tegra@vger.kernel.org
Subject: Re: (subset) [PATCH 20/20] soc/tegra: cbb: remove MODULE_LICENSE in non-modules
Date: Wed, 5 Apr 2023 15:09:50 +0200 [thread overview]
Message-ID: <168070017411.4044223.332660591498857046.b4-ty@nvidia.com> (raw)
In-Reply-To: <20230228130215.289081-21-nick.alcock@oracle.com>
From: Thierry Reding <treding@nvidia.com>
On Tue, 28 Feb 2023 13:02:15 +0000, Nick Alcock 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.
>
> [...]
Applied, thanks!
[20/20] soc/tegra: cbb: remove MODULE_LICENSE in non-modules
(no commit info)
Best regards,
--
Thierry Reding <treding@nvidia.com>
next prev parent reply other threads:[~2023-04-05 13:10 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 13:01 [PATCH 00/20] MODULE_LICENSE removals, fifth tranche Nick Alcock
2023-02-28 13:01 ` Nick Alcock
2023-02-28 13:01 ` [PATCH 01/20] perf/hw_breakpoint: remove MODULE_LICENSE in non-modules Nick Alcock
2023-02-28 13:01 ` [PATCH 02/20] pinctrl: amd: " Nick Alcock
2023-03-07 13:08 ` Linus Walleij
2023-02-28 13:01 ` [PATCH 03/20] pinctrl: mediatek: " Nick Alcock
2023-02-28 13:01 ` Nick Alcock
2023-02-28 13:01 ` [PATCH 04/20] pinctrl: renesas: " Nick Alcock
2023-02-28 13:02 ` [PATCH 05/20] lib: " Nick Alcock
2023-02-28 16:35 ` Keller, Jacob E
2023-02-28 13:02 ` [PATCH 06/20] powercap: " Nick Alcock
2023-02-28 20:33 ` Rafael J. Wysocki
2023-02-28 13:02 ` [PATCH 07/20] power: supply: " Nick Alcock
2023-02-28 13:02 ` [PATCH 08/20] remoteproc: " Nick Alcock
2023-02-28 13:35 ` Mukesh Ojha
2023-03-02 22:01 ` Mathieu Poirier
2023-02-28 13:02 ` [PATCH 09/20] clk: renesas: " Nick Alcock
2023-02-28 13:45 ` Geert Uytterhoeven
2023-02-28 14:07 ` Adam Ford
2023-03-20 11:08 ` Nick Alcock
2023-02-28 13:02 ` [PATCH 10/20] reset: mchp: sparx5: " Nick Alcock
2023-02-28 13:02 ` Nick Alcock
2023-02-28 14:53 ` Steen Hegelund
2023-02-28 14:53 ` Steen Hegelund
2023-02-28 13:02 ` [PATCH 11/20] reset: lantiq: " Nick Alcock
2023-02-28 13:02 ` [PATCH 12/20] clk: microchip: mpfs: " Nick Alcock
2023-02-28 13:02 ` Nick Alcock
2023-02-28 19:19 ` Conor Dooley
2023-02-28 19:19 ` Conor Dooley
2023-02-28 13:02 ` [PATCH 13/20] reset: " Nick Alcock
2023-02-28 13:02 ` Nick Alcock
2023-02-28 19:17 ` Conor Dooley
2023-02-28 19:17 ` Conor Dooley
2023-02-28 19:26 ` Nick Alcock
2023-02-28 19:26 ` Nick Alcock
2023-02-28 19:53 ` Conor Dooley
2023-02-28 19:53 ` Conor Dooley
2023-02-28 13:02 ` [PATCH 14/20] rv/reactor: " Nick Alcock
2023-02-28 13:19 ` Daniel Bristot de Oliveira
2023-02-28 13:02 ` [PATCH 15/20] tty: serial: imx: " Nick Alcock
2023-02-28 13:02 ` Nick Alcock
2023-02-28 13:02 ` [PATCH 16/20] irqchip/irq-sl28cpld: " Nick Alcock
2023-02-28 16:12 ` Michael Walle
2023-02-28 13:02 ` [PATCH 17/20] ARC: reset: " Nick Alcock
2023-02-28 13:02 ` [PATCH 18/20] " Nick Alcock
2023-02-28 13:02 ` [PATCH 19/20] power: " Nick Alcock
2023-02-28 13:02 ` [PATCH 20/20] soc/tegra: cbb: " Nick Alcock
2023-04-05 13:09 ` Thierry Reding [this message]
2023-02-28 13:47 ` [PATCH 00/20] MODULE_LICENSE removals, fifth tranche Geert Uytterhoeven
2023-02-28 13:47 ` Geert Uytterhoeven
2023-03-20 11:06 ` Nick Alcock
2023-03-20 11:06 ` Nick Alcock
2023-03-09 16:14 ` Greg KH
2023-03-09 16:14 ` Greg KH
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=168070017411.4044223.332660591498857046.b4-ty@nvidia.com \
--to=thierry.reding@gmail.com \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=nick.alcock@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.