From: Will Deacon <will@kernel.org>
To: mcgrof@kernel.org, Nick Alcock <nick.alcock@oracle.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
linux-gpio@vger.kernel.org, linux-edac@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-acpi@vger.kernel.org, linux-samsung-soc@vger.kernel.org,
linux-modules@vger.kernel.org, dmaengine@vger.kernel.org,
linux-actions@lists.infradead.org, linux-serial@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-sunxi@lists.linux.dev,
asahi@lists.linux.dev, linux-pci@vger.kernel.org
Subject: Re: [PATCH 00/24] MODULE_LICENSE removals, second tranche
Date: Mon, 27 Mar 2023 16:01:15 +0100 [thread overview]
Message-ID: <167992609868.3834946.4831319626649638477.b4-ty@kernel.org> (raw)
In-Reply-To: <20230217141059.392471-1-nick.alcock@oracle.com>
On Fri, 17 Feb 2023 14:10:35 +0000, Nick Alcock wrote:
> This series, based on current modules-next, is part of a treewide cleanup
> suggested by Luis Chamberlain, to remove the LICENSE_MODULE usage from
> files/objects that are not tristate. Due to recent changes to kbuild, these
> uses are now problematic. See the commit logs for more details.
>
> (The commit log prefixes and Cc lists are automatically determined using
> the script mentioned below. I've eyeballed them, and they seem reasonable:
> my apologies if they are not.)
>
> [...]
Applied drivers/perf patch to will (for-next/perf), thanks!
[08/24] kbuild, drivers/perf: remove MODULE_LICENSE in non-modules
https://git.kernel.org/will/c/a64021d3726a
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-03-27 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 14:10 [PATCH 00/24] MODULE_LICENSE removals, second tranche Nick Alcock
2023-02-17 14:10 ` [PATCH 09/24] kbuild, ARM: tegra: remove MODULE_LICENSE in non-modules Nick Alcock
2023-04-05 13:09 ` (subset) " Thierry Reding
2023-03-27 15:01 ` Will Deacon [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=167992609868.3834946.4831319626649638477.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=asahi@lists.linux.dev \
--cc=catalin.marinas@arm.com \
--cc=dmaengine@vger.kernel.org \
--cc=kernel-team@android.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-actions@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--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 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).