From: Conor Dooley <conor@kernel.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Nick Alcock" <nick.alcock@oracle.com>,
mcgrof@kernel.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Rob Herring" <robh@kernel.org>,
"Shawn Guo" <shawn.guo@linaro.org>,
"Karthikeyan Mitran" <m.karthikeyan@mobiveil.co.in>,
"Hou Zhiqiang" <Zhiqiang.Hou@nxp.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Manivannan Sadhasivam" <mani@kernel.org>,
"Kishon Vijay Abraham I" <kishon@kernel.org>,
"Leon Romanovsky" <leon@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Hitomi Hasegawa" <hasegawa-hitomi@fujitsu.com>
Subject: Re: [PATCH v2 0/7] MODULE_LICENSE removals, first tranche
Date: Thu, 16 Feb 2023 18:01:23 +0000 [thread overview]
Message-ID: <Y+5vczghnTF5nUut@spud> (raw)
In-Reply-To: <20230216174333.GA3313434@bhelgaas>
[-- Attachment #1: Type: text/plain, Size: 3388 bytes --]
On Thu, Feb 16, 2023 at 11:43:33AM -0600, Bjorn Helgaas wrote:
> [+cc PCI folks, who got the patches but not this cover letter, and
> participants from the v1 posting]
Thanks Bjorn..
> On Thu, Feb 16, 2023 at 03:24:03PM +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.)
> >
> > This is a small initial tranche to see if the general approach is valid:
> > larger tranches can follow if desired and if these patches seem OK.
> > I'll be sending a second 24-patch tranche in a few hours if this
> > one meets with general approval.
> >
> > (In total, there are 121 patches in this series.)
> >
> >
> > Differences from v1:
> > - just remove MODULE_LICENSE, don't comment it out
> > - Cc: paid maintainers as well as unpaid ones
> > - improvements to the prefix determination code (notable in
> > PCI: versatile in particular)
> >
> > The series at a whole can be found here:
> > https://github.com/nickalcock/linux module-license
> >
> > The patch splitter (not for upstreaming!) used to prepare these
> > commits can be found here:
> > https://github.com/nickalcock/linux mass-split
> >
> > Cc: Luis Chamberlain <mcgrof@kernel.org>
> > Cc: linux-modules@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> >
> > Nick Alcock (7):
> > kbuild, PCI: versatile: remove MODULE_LICENSE in non-modules
> > kbuild, PCI: mobiveil: remove MODULE_LICENSE in non-modules
> > kbuild, PCI: tegra: remove MODULE_LICENSE in non-modules
> > kbuild, PCI: endpoint: remove MODULE_LICENSE in non-modules
> > kbuild, PCI: hip: remove MODULE_LICENSE in non-modules
> > kbuild, shpchp: remove MODULE_LICENSE in non-modules
> > kbuild, PCI: dwc: remove MODULE_LICENSE in non-modules
> >
> > drivers/pci/controller/dwc/pcie-histb.c | 1 -
> > drivers/pci/controller/mobiveil/pcie-mobiveil-plat.c | 1 -
> > drivers/pci/controller/pci-tegra.c | 1 -
> > drivers/pci/controller/pci-versatile.c | 1 -
> > drivers/pci/controller/pcie-hisi-error.c | 1 -
> > drivers/pci/endpoint/pci-ep-cfs.c | 1 -
> > drivers/pci/endpoint/pci-epc-core.c | 1 -
> > drivers/pci/endpoint/pci-epc-mem.c | 1 -
> > drivers/pci/endpoint/pci-epf-core.c | 1 -
> > drivers/pci/hotplug/shpchp_core.c | 1 -
> > 10 files changed, 10 deletions(-)
>
> I squashed these and applied to pci/kbuild for v6.3, thanks!
>
> I added examples from the v1 posting to the commit log; let me know if
> I got anything wrong:
I noticed that (as requested!) Nick dropped the change to the microchip
driver.
Would you like me to resend patch 3/11 of [1] to clear the decks of
"incorrect" MODULE_LICENSE usage?
Thanks,
Conor.
1 - https://lore.kernel.org/linux-pci/20230111125323.1911373-4-daire.mcnamara@microchip.com/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-02-16 18:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 15:24 [PATCH v2 0/7] MODULE_LICENSE removals, first tranche Nick Alcock
2023-02-16 15:24 ` [PATCH v2 1/7] kbuild, PCI: versatile: remove MODULE_LICENSE in non-modules Nick Alcock
2023-02-16 15:24 ` [PATCH v2 2/7] kbuild, PCI: mobiveil: " Nick Alcock
2023-02-16 15:24 ` [PATCH v2 3/7] kbuild, PCI: tegra: " Nick Alcock
2023-02-16 15:24 ` [PATCH v2 4/7] kbuild, PCI: endpoint: " Nick Alcock
2023-02-16 18:11 ` Manivannan Sadhasivam
2023-02-16 15:24 ` [PATCH v2 5/7] kbuild, PCI: hip: " Nick Alcock
2023-02-16 15:24 ` [PATCH v2 6/7] kbuild, shpchp: " Nick Alcock
2023-02-16 15:24 ` [PATCH v2 7/7] kbuild, PCI: dwc: " Nick Alcock
2023-02-16 17:43 ` [PATCH v2 0/7] MODULE_LICENSE removals, first tranche Bjorn Helgaas
2023-02-16 18:01 ` Conor Dooley [this message]
2023-02-16 19:16 ` Bjorn Helgaas
2023-02-16 23:38 ` Conor Dooley
2023-02-16 19:20 ` 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=Y+5vczghnTF5nUut@spud \
--to=conor@kernel.org \
--cc=Zhiqiang.Hou@nxp.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=hasegawa-hitomi@fujitsu.com \
--cc=helgaas@kernel.org \
--cc=kishon@kernel.org \
--cc=kw@linux.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=m.karthikeyan@mobiveil.co.in \
--cc=mani@kernel.org \
--cc=mcgrof@kernel.org \
--cc=nick.alcock@oracle.com \
--cc=robh@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=thierry.reding@gmail.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