From: Leon Romanovsky <leon@kernel.org>
To: Hongtao Wu <wuht06@gmail.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Orson Zhai <orsonzhai@gmail.com>,
Baolin Wang <baolin.wang7@gmail.com>,
Chunyan Zhang <zhang.lyra@gmail.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Hongtao Wu <billows.wu@unisoc.com>
Subject: Re: [RESEND PATCH v5 2/2] PCI: sprd: Add support for Unisoc SoCs' PCIe controller
Date: Thu, 14 Jan 2021 15:06:24 +0200 [thread overview]
Message-ID: <20210114130624.GR4678@unreal> (raw)
In-Reply-To: <CAG_R4_UJ0=8=31XZD-SiiuL91M02N+fn=CLNA4_5Xm7jRDE1Rg@mail.gmail.com>
On Thu, Jan 14, 2021 at 08:00:50PM +0800, Hongtao Wu wrote:
> On Thu, Jan 14, 2021 at 4:52 PM Leon Romanovsky <leon@kernel.org> wrote:
> >
> > On Thu, Jan 14, 2021 at 04:29:28PM +0800, Hongtao Wu wrote:
> > > From: Hongtao Wu <billows.wu@unisoc.com>
> > >
> > > This series adds PCIe controller driver for Unisoc SoCs.
> > > This controller is based on DesignWare PCIe IP.
> > >
> > > Signed-off-by: Hongtao Wu <billows.wu@unisoc.com>
> > > ---
> > > drivers/pci/controller/dwc/Kconfig | 12 ++
> > > drivers/pci/controller/dwc/Makefile | 1 +
> > > drivers/pci/controller/dwc/pcie-sprd.c | 293 +++++++++++++++++++++++++++++++++
> > > 3 files changed, 306 insertions(+)
> > > create mode 100644 drivers/pci/controller/dwc/pcie-sprd.c
> >
> > <...>
> >
> > > +static struct platform_driver sprd_pcie_driver = {
> > > + .probe = sprd_pcie_probe,
> > > + .remove = __exit_p(sprd_pcie_remove),
> > ^^^^^^ why is that?
> >
>
> Thanks for the review.
>
> I think that if 'MODULE' is defined, '.remove = sprd_pcie_remove',
> else '.remove = NULL'.
> I would appreciate hearing your opinion about this.
If module not defined, these .probe and .remove won't be called.
>
> > > + .driver = {
> > > + .name = "sprd-pcie",
> > > + .of_match_table = sprd_pcie_of_match,
> > > + },
> > > +};
> > > +
> > > +module_platform_driver(sprd_pcie_driver);
> > > +
> > > +MODULE_DESCRIPTION("Unisoc PCIe host controller driver");
> > > +MODULE_LICENSE("GPL v2");
> >
> > I think that it needs to be "GPL" and not "GPL v2".
> >
>
> Many platform drivers use 'GPL v2', but others use 'GPL'.
> I am not sure whether to use 'GPL' or 'GPL v2'.
> Could you tell me why ‘GPL’ is needed here?
Because GPL already means v2, see Documentation/process/license-rules.rst
447
448 "GPL v2" Same as "GPL". It exists for historic
449 reasons.
>
> > Thanks
> >
> > > --
> > > 2.7.4
> > >
next prev parent reply other threads:[~2021-01-14 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 8:29 [RESEND PATCH v5 0/2] PCI: Add new Unisoc PCIe driver Hongtao Wu
2021-01-14 8:29 ` [RESEND PATCH v5 1/2] dt-bindings: PCI: sprd: Document Unisoc PCIe RC host controller Hongtao Wu
2021-01-14 8:29 ` [RESEND PATCH v5 2/2] PCI: sprd: Add support for Unisoc SoCs' PCIe controller Hongtao Wu
2021-01-14 8:52 ` Leon Romanovsky
2021-01-14 10:49 ` Hongtao Wu
2021-01-14 12:00 ` Hongtao Wu
2021-01-14 13:06 ` Leon Romanovsky [this message]
2021-01-14 13:30 ` Hongtao Wu
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=20210114130624.GR4678@unreal \
--to=leon@kernel.org \
--cc=baolin.wang7@gmail.com \
--cc=billows.wu@unisoc.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=orsonzhai@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wuht06@gmail.com \
--cc=zhang.lyra@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