From: Nick Alcock <nick.alcock@oracle.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: mcgrof@kernel.org, linux-modules@vger.kernel.org,
linux-kernel@vger.kernel.org, Rob Herring <robh@kernel.org>,
linux-pci@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/8] kbuild, PCI: generic,versatile: comment out MODULE_LICENSE in non-modules
Date: Thu, 16 Feb 2023 13:34:30 +0000 [thread overview]
Message-ID: <87r0upvimx.fsf@esperi.org.uk> (raw)
In-Reply-To: <20230214172053.GA3044917@bhelgaas> (Bjorn Helgaas's message of "Tue, 14 Feb 2023 11:20:53 -0600")
On 14 Feb 2023, Bjorn Helgaas uttered the following:
> On Tue, Feb 14, 2023 at 03:41:32PM +0000, Nick Alcock wrote:
>> On 13 Feb 2023, Bjorn Helgaas spake thusly:
>> > On Fri, Feb 10, 2023 at 04:47:42PM +0000, Nick Alcock wrote:
>
>> > - Please follow the subject line convention for each file. They're
>> > mostly there after dropping "kbuild", but do capitalize the
>> > sentence that follows the prefix. The prefix should always be
>> > "PCI/<driver-tag>: "
>
> I misspoke about "PCI/<driver-tag>". I use "PCI/<feature>" for things
> like MSI, AER, ASPM, etc. "PCI: <driver-tag>" is the usual pattern
> for things specific to a driver, and it sounds like this is what
> you've already done:
>
> $ git log --oneline drivers/pci/controller/pci-versatile.c
> 6086987bdeb5 PCI: versatile: Remove redundant variable retval
> b64aa11eb2dd PCI: Set bridge map_irq and swizzle_irq to default functions
> 669cbc708122 PCI: Move DT resource setup into devm_pci_alloc_host_bridge()
> d3bb94d06aae PCI: Drop unnecessary zeroing of bridge fields
> 6a589900d050 PCI: Set default bridge parent device
> 79cbde56f98b PCI: versatile: Drop flag PCI_ENABLE_PROC_DOMAINS
> 3cf0eead9fb8 PCI: controller: Convert to devm_platform_ioremap_resource()
> a4b21b858b56 PCI: versatile: Use pci_host_probe() to register host
> 331f63457165 PCI: of: Add inbound resource parsing to helpers
> 2999dea8e94a PCI: versatile: Remove usage of PHYS_OFFSET
> f9f4fdaa3509 PCI: versatile: Use pci_parse_request_of_pci_ranges()
> 0018b265adf7 PCI: versatile: Fix I/O space page leak
Oh good, that's what I was hoping.
After a bunch more bugfixing It's coming out as 'kbuild, PCI: versatile"
now. (This seems better than 'kbuild: PCI: versatile' because 'PCI:
versatile' isn't a subsystem of 'kbuild'.)
>> ... If the rules for generating prefixes vary by subsystem this means
>> I'll have to fight through God knows how many annoyed maintainers to get
>> this incredibly trivial change in.)
>
> I think your script generally does the right thing, and it's already
> far more than most folks do, so thank you for that!
Heh, I knew it wouldn't be time totally wasted: I've saved time already
on account of having had to redo the individual patches in some way
eight or nine times by now, and being able to make the changes in one go
and split it out into separate commits after that was definitely easier
than the alternative.
FYI: the splitting script's improved a bit. it's still an undocumented,
uncommented horror, but it now supports arbitrary regex-replacements of
"bad prefixes" in a file prefix-transforms.yaml, for this run containing
treewide: ''
fix spelling mistake: ''
task_get_unused_fd_flags: ''
x86/mm/dump_pagetables: 'mm'
I stuffed the splitting script in
https://github.com/nickalcock/linux.git mass-split (as
scripts/kernel-mass-split) just in case it's useful to someone else.
Definitely absolutely not for upstreaming!
(Next tranche coming soon, the previous set again -- improved as
suggested, removing MODULE_LICENSE instead of commenting out, etc -- and
then another, bigger tranche inflicted on a different subset of
maintainers.)
--
NULL && (void)
next prev parent reply other threads:[~2023-02-16 13:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 16:47 [PATCH 0/8] MODULE_LICENSE removals, first tranche Nick Alcock
2023-02-10 16:47 ` [PATCH 1/8] kbuild, PCI: generic,versatile: comment out MODULE_LICENSE in non-modules Nick Alcock
2023-02-10 17:36 ` Rob Herring
2023-02-10 18:43 ` Nick Alcock
2023-02-13 22:57 ` Bjorn Helgaas
2023-02-14 15:41 ` Nick Alcock
2023-02-14 17:20 ` Bjorn Helgaas
2023-02-16 13:34 ` Nick Alcock [this message]
2023-02-10 16:47 ` [PATCH 2/8] kbuild, PCI: mobiveil: " Nick Alcock
2023-02-10 16:47 ` [PATCH 3/8] kbuild, ARM: tegra: " Nick Alcock
2023-02-10 16:47 ` [PATCH 4/8] kbuild, PCI: endpoint: " Nick Alcock
2023-02-10 16:47 ` [PATCH 5/8] kbuild, PCI: hip: " Nick Alcock
2023-02-10 16:47 ` [PATCH 6/8] kbuild, shpchp: " Nick Alcock
2023-02-10 16:47 ` [PATCH 7/8] kbuild, PCI: dwc: histb: " Nick Alcock
2023-02-10 16:47 ` [PATCH 8/8] kbuild, PCI: microchip: " Nick Alcock
2023-02-10 18:27 ` Conor Dooley
2023-02-10 19:26 ` Nick Alcock
2023-02-10 20:10 ` Conor Dooley
2023-02-12 18:37 ` Leon Romanovsky
2023-02-12 19:52 ` Nick Alcock
2023-02-13 15:53 ` Nick Alcock
2023-02-13 16:13 ` Nick Alcock
2023-02-13 16:51 ` Conor Dooley
2023-02-13 17:06 ` Leon Romanovsky
2023-02-15 19:06 ` Nick Alcock
2023-02-13 17:30 ` Jonathan Corbet
2023-02-13 19:23 ` Leon Romanovsky
2023-02-16 12:05 ` 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=87r0upvimx.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=helgaas@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=robh@kernel.org \
/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).