linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH 13/20] reset: remove MODULE_LICENSE in non-modules
Date: Tue, 28 Feb 2023 19:53:10 +0000	[thread overview]
Message-ID: <Y/5bpr/93hJ3yYUU@spud> (raw)
In-Reply-To: <87edq9h9q8.fsf@esperi.org.uk>

[-- Attachment #1: Type: text/plain, Size: 2451 bytes --]

On Tue, Feb 28, 2023 at 07:26:55PM +0000, Nick Alcock wrote:
> [dropped non-lists to defend innocent ears from my flaming pedantry]
> 
> On 28 Feb 2023, Conor Dooley stated:
> 
> > On Tue, Feb 28, 2023 at 01:02:08PM +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.
> >> 
> >> So remove it in the files in this commit, none of which can be built as
> >> modules.
> >> 
> >> Signed-off-by: Nick Alcock <nick.alcock@oracle.com>
> >> Suggested-by: Luis Chamberlain <mcgrof@kernel.org>
> >> Cc: Luis Chamberlain <mcgrof@kernel.org>
> >> Cc: linux-modules@vger.kernel.org
> >> Cc: linux-kernel@vger.kernel.org
> >> Cc: Hitomi Hasegawa <hasegawa-hitomi@fujitsu.com>
> >> Cc: Conor Dooley <conor.dooley@microchip.com>
> >> Cc: Daire McNamara <daire.mcnamara@microchip.com>
> >> Cc: Philipp Zabel <p.zabel@pengutronix.de>
> >> Cc: linux-riscv@lists.infradead.org
> >> ---
> >>  drivers/reset/reset-mpfs.c | 1 -
> >
> > I assume your script just got confused here w/ $subject, since there's
> > only a change for this specific file.
> 
> This file has had no commits since you wrote it last year, and the
> subject for that commit was
> 
>     reset: add polarfire soc reset support
> 
> so, er, yes, the script used 'reset:' as a prefix, mimicking the
> existing commit. I'm not sure what else it could have done.

Oh ye, silly me - I didn't think of that. I guess that's a common
pattern for commits adding a driver, as the "mpfs:" doesn't really make
sense until the driver is in-tree.
I'm not too sure what you could have done either, but I'm not
complaining, or requesting that something be changed here.

> (Regarding the rest of the subject line, I suppose I could have arranged
> to detect single-file commits and turned the subject into 'in this
> non-module'? But there comes a time when even I think that maybe I might
> be overdesigning something, and automated grammatical adjustments to the
> subject line was that point!)

Yeah, I think it's not worth doing anything about really...

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-02-28 19:53 UTC|newest]

Thread overview: 40+ 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 ` [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 ` [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 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 19:19   ` Conor Dooley
2023-02-28 13:02 ` [PATCH 13/20] reset: " Nick Alcock
2023-02-28 19:17   ` Conor Dooley
2023-02-28 19:26     ` Nick Alcock
2023-02-28 19:53       ` Conor Dooley [this message]
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 ` [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   ` (subset) " Thierry Reding
2023-02-28 13:47 ` [PATCH 00/20] MODULE_LICENSE removals, fifth tranche Geert Uytterhoeven
2023-03-20 11:06   ` Nick Alcock
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=Y/5bpr/93hJ3yYUU@spud \
    --to=conor@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.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 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).