From: Mark Brown <broonie@kernel.org>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: mcgrof@kernel.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org,
Hitomi Hasegawa <hasegawa-hitomi@fujitsu.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 13/17] regulator: stm32-pwr: remove MODULE_LICENSE in non-modules
Date: Fri, 3 Mar 2023 00:31:58 +0000 [thread overview]
Message-ID: <ZAE//jJ0GHvLN1m2@sirena.org.uk> (raw)
In-Reply-To: <20230302211759.30135-14-nick.alcock@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
On Thu, Mar 02, 2023 at 09:17:55PM +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
You've not copied me on the rest of the series so I'm not sure
what's going on with dependencies. What's the story here?
When sending a patch series it is important to ensure that all
the various maintainers understand what the relationship between
the patches as the expecation is that there will be
interdependencies. Either copy everyone on the whole series or
at least copy them on the cover letter and explain what's going
on. If there are no strong interdependencies then it's generally
simplest to just send the patches separately to avoid any
possible confusion.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-03-03 0:34 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 21:17 [PATCH 00/17] MODULE_LICENSE removals, sixth tranche Nick Alcock
2023-03-02 21:17 ` [PATCH 01/17] irqchip: remove MODULE_LICENSE in non-modules Nick Alcock
2023-03-02 21:17 ` [PATCH 02/17] bus: " Nick Alcock
2023-03-02 21:17 ` [PATCH 03/17] braille_console: " Nick Alcock
2023-03-02 21:17 ` [PATCH 04/17] arm-cci: " Nick Alcock
2023-03-02 21:17 ` [PATCH 05/17] drivers: bus: simple-pm-bus: " Nick Alcock
2023-03-03 7:52 ` Geert Uytterhoeven
2023-03-03 18:32 ` Nick Alcock
2023-03-03 18:43 ` Geert Uytterhoeven
2023-03-20 10:58 ` Nick Alcock
2023-03-02 21:17 ` [PATCH 06/17] watch_queue: " Nick Alcock
2023-03-02 21:17 ` [PATCH 07/17] btree: " Nick Alcock
2023-03-02 21:17 ` [PATCH 08/17] lib: " Nick Alcock
2023-03-02 21:17 ` [PATCH 09/17] fprobe: " Nick Alcock
2023-03-02 21:17 ` [PATCH 10/17] tty: " Nick Alcock
2023-03-09 16:15 ` Greg Kroah-Hartman
2023-03-09 22:38 ` Luis Chamberlain
2023-03-10 7:31 ` Greg Kroah-Hartman
2023-03-10 19:33 ` Luis Chamberlain
2023-03-24 9:08 ` Geert Uytterhoeven
2023-03-24 9:12 ` Geert Uytterhoeven
2023-03-24 9:14 ` Greg Kroah-Hartman
2023-03-24 9:16 ` Geert Uytterhoeven
2023-03-24 14:16 ` Nick Alcock
2023-03-24 14:29 ` Greg Kroah-Hartman
2023-03-24 18:06 ` Luis Chamberlain
2023-03-27 10:46 ` Nick Alcock
2023-03-27 11:43 ` Greg Kroah-Hartman
2023-03-27 14:54 ` Nick Alcock
2023-03-27 18:23 ` Nick Alcock
2023-03-29 2:50 ` Luis Chamberlain
2023-04-13 20:24 ` Luis Chamberlain
2023-03-26 4:52 ` Christoph Hellwig
2023-03-02 21:17 ` [PATCH 11/17] unicode: " Nick Alcock
2023-03-06 15:32 ` Gabriel Krisman Bertazi
2023-03-02 21:17 ` [PATCH 12/17] udmabuf: " Nick Alcock
2023-03-02 21:17 ` [PATCH 13/17] regulator: stm32-pwr: " Nick Alcock
2023-03-03 0:31 ` Mark Brown [this message]
2023-03-03 18:30 ` Nick Alcock
2023-03-04 20:12 ` Mark Brown
2023-03-02 21:17 ` [PATCH 14/17] mm: " Nick Alcock
2023-03-02 21:17 ` [PATCH 15/17] xen: " Nick Alcock
2023-03-06 7:45 ` Juergen Gross
2023-03-02 21:17 ` [PATCH 16/17] zpool: " Nick Alcock
2023-03-02 21:17 ` [PATCH 17/17] zswap: " Nick Alcock
2023-03-03 22:22 ` [PATCH 00/17] MODULE_LICENSE removals, sixth tranche Luis Chamberlain
2023-03-20 11:00 ` Nick Alcock
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=ZAE//jJ0GHvLN1m2@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcgrof@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--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
all inboxes | Powered by JetHome®