From: Bjorn Helgaas <helgaas@kernel.org>
To: Nick Alcock <nick.alcock@oracle.com>
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: Tue, 14 Feb 2023 11:20:53 -0600 [thread overview]
Message-ID: <20230214172053.GA3044917@bhelgaas> (raw)
In-Reply-To: <873578xnir.fsf@esperi.org.uk>
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
> ... 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!
I normally do that sort of minimal fixup silently when applying
because there's no point in reposting when it's faster to make those
trivial edits myself. In this case, removing MODULE_LICENSE instead
of commenting it out is just a little more than I like to do when
keeping your signed-off-by.
Bjorn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-14 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230210164749.368998-1-nick.alcock@oracle.com>
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 [this message]
2023-02-16 13:34 ` 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=20230214172053.GA3044917@bhelgaas \
--to=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=nick.alcock@oracle.com \
--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).