From: Kevin Hilman <khilman@baylibre.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Cc: linux-pci@vger.kernel.org,
Neil Armstrong <narmstrong@baylibre.com>,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org,
Yue Wang <yue.wang@amlogic.com>
Subject: Re: [PATCH] pci: meson: build as module by default
Date: Fri, 02 Oct 2020 11:53:27 -0700 [thread overview]
Message-ID: <7h362wmpco.fsf@baylibre.com> (raw)
In-Reply-To: <20200928163440.GA16986@e121166-lin.cambridge.arm.com>
Hi Lorenzo,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> writes:
> On Fri, Sep 18, 2020 at 11:12:51AM -0700, Kevin Hilman wrote:
>> Enable pci-meson to build as a module whenever ARCH_MESON is enabled.
>>
>> Cc: Yue Wang <yue.wang@amlogic.com>
>> Signed-off-by: Kevin Hilman <khilman@baylibre.com>
>> ---
>> Tested on Khadas VIM3 and Khadas VIM3 using NVMe SSD devices.
>>
>> drivers/pci/controller/dwc/Kconfig | 3 ++-
>> drivers/pci/controller/dwc/pci-meson.c | 8 +++++++-
>> 2 files changed, 9 insertions(+), 2 deletions(-)
>
> Applied to pci/meson, thanks.
Rob pointed out that the MODULE_LICENCE wasn't the same as the SPDX
header. Could you squash the update below before submitting?
Thanks,
Kevin
diff --git a/drivers/pci/controller/dwc/pci-meson.c b/drivers/pci/controller/dwc/pci-meson.c
index 7a1fb55ee44a..35b167e907aa 100644
--- a/drivers/pci/controller/dwc/pci-meson.c
+++ b/drivers/pci/controller/dwc/pci-meson.c
@@ -604,4 +604,4 @@ module_platform_driver(meson_pcie_driver);
MODULE_AUTHOR("Yue Wang <yue.wang@amlogic.com>");
MODULE_DESCRIPTION("Amlogic PCIe Controller driver");
-MODULE_LICENSE("Dual BSD/GPL");
+MODULE_LICENSE("GPL v2");
next prev parent reply other threads:[~2020-10-02 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-18 18:12 [PATCH] pci: meson: build as module by default Kevin Hilman
2020-09-21 15:34 ` Neil Armstrong
2020-09-25 21:13 ` Rob Herring
2020-09-28 16:34 ` Lorenzo Pieralisi
2020-10-02 18:53 ` Kevin Hilman [this message]
2020-10-05 12:03 ` Lorenzo Pieralisi
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=7h362wmpco.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=narmstrong@baylibre.com \
--cc=yue.wang@amlogic.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