From: "Krzysztof Wilczyński" <kw@linux.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Sergio Paracuellos <sergio.paracuellos@gmail.com>,
linux-pci <linux-pci@vger.kernel.org>,
"open list:BROADCOM NVRAM DRIVER" <linux-mips@vger.kernel.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
John Crispin <john@phrozen.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Yanteng Si <siyanteng@loongson.cn>
Subject: Re: [PATCH 4/5] PCI: mt7621: Add missing 'MODULE_LICENSE()' definition
Date: Mon, 15 Nov 2021 22:50:48 +0100 [thread overview]
Message-ID: <YZLWOFGFs4g6gh5l@rocinante> (raw)
In-Reply-To: <CAK8P3a0A9xAcwDLFbUk--X2+7gFpOL7HJw-9Sk8KZxfoidcxuw@mail.gmail.com>
Hi Arnd,
[...]
> > > builtin_platform_driver(mt7621_pci_driver);
> > > +
> > > +MODULE_LICENSE("GPL v2");
> >
> > A question here about the builtin_platform_driver() use in this driver,
> > especially since it's set as tristate in Kconfig, thus I am not sure if
> > using builtin_platform_driver() over module_platform_driver() is correct?
> >
> > Unless this is more because you need to reply on device_initcall() for the
> > driver to properly initialise?
>
> builtin_platform_driver() does the right thing for loadable modules that
> have no module-unload and are not intended to be removable.
>
> This is often use for PCI drivers, but after Rob reworked this code a while
> back, it should actually be possible to reliably remove and reload PCI
> host bridge drivers, and it would be good to eventually lift the restriction
> here as well.
Thank you for letting me know. Much appreciated. I assumed in the past
that with tristate in Kconfig the module_platform_driver() would be the
preferred route.
Krzysztof
next prev parent reply other threads:[~2021-11-15 21:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 7:08 [PATCH 0/5] PCI: mt7621: remove specific MIPS code from driver Sergio Paracuellos
2021-11-15 7:08 ` [PATCH 1/5] PCI: let 'pcibios_root_bridge_prepare()' access to 'bridge->windows' Sergio Paracuellos
2021-11-19 23:20 ` Bjorn Helgaas
2021-12-01 20:24 ` Bjorn Helgaas
2021-12-01 20:50 ` Arnd Bergmann
2021-12-01 20:56 ` Sergio Paracuellos
2021-12-01 21:12 ` Bjorn Helgaas
2021-12-01 20:27 ` Bjorn Helgaas
2021-11-15 7:08 ` [PATCH 2/5] MIPS: ralink: implement 'pcibios_root_bridge_prepare()' Sergio Paracuellos
2021-11-15 7:08 ` [PATCH 3/5] PCI: mt7621: avoid custom MIPS code in driver code Sergio Paracuellos
2021-12-01 18:16 ` Bjorn Helgaas
2021-12-01 19:25 ` Sergio Paracuellos
2021-11-15 7:08 ` [PATCH 4/5] PCI: mt7621: Add missing 'MODULE_LICENSE()' definition Sergio Paracuellos
2021-11-15 12:44 ` Krzysztof Wilczyński
2021-11-15 13:00 ` Arnd Bergmann
2021-11-15 13:51 ` Sergio Paracuellos
2021-11-15 13:55 ` Arnd Bergmann
2021-11-15 21:50 ` Krzysztof Wilczyński [this message]
2021-11-15 21:52 ` Krzysztof Wilczyński
2021-11-15 7:08 ` [PATCH 5/5] PCI: mt7621: Kconfig: completely enable driver for 'COMPILE_TEST' Sergio Paracuellos
2021-12-01 20:12 ` Bjorn Helgaas
2021-12-01 20:33 ` Sergio Paracuellos
2021-11-17 12:41 ` [PATCH 0/5] PCI: mt7621: remove specific MIPS code from driver Thomas Bogendoerfer
2021-11-17 12:48 ` Sergio Paracuellos
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=YZLWOFGFs4g6gh5l@rocinante \
--to=kw@linux.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=john@phrozen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sergio.paracuellos@gmail.com \
--cc=siyanteng@loongson.cn \
--cc=tsbogend@alpha.franken.de \
/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