From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: Tanmay Shah <tanmays@amd.com>
Cc: andersson@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, michal.simek@xilinx.com,
ben.levinsky@xilinx.com, tanmay.shah@xilinx.com,
michal.simek@amd.com, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v9 6/6] drivers: remoteproc: Add Xilinx r5 remoteproc driver
Date: Thu, 29 Sep 2022 11:22:00 -0600 [thread overview]
Message-ID: <20220929172200.GB3107608@p14s> (raw)
In-Reply-To: <d1cfa787-9f8e-fe8a-d816-0bd8c3a3244d@amd.com>
On Mon, Sep 26, 2022 at 03:02:22PM -0700, Tanmay Shah wrote:
>
> On 9/1/22 1:25 PM, Mathieu Poirier wrote:
> > On Thu, Jul 07, 2022 at 06:39:55PM -0700, Tanmay Shah wrote:
> [ ... ]
> > > --- /dev/null
> > > +++ b/drivers/remoteproc/xlnx_r5_remoteproc.c
> > > @@ -0,0 +1,1055 @@
> > > +// SPDX-License-Identifier: GPL-2.0
>
> Hi Mathieu,
>
> I tried to fix SPDX-License-Identifier to GPL (same as MODULE_LICENSE
> below), However checkpatch.pl reports this as following warning:
>
> "WARNING: 'SPDX-License-Identifier: GPL' is not supported in LICENSES/..."
>
> I see that GPL-1.0 is under LICENSE/deprecated directory.
>
> > > +/*
> > > + * ZynqMP R5 Remote Processor driver
> > > + *
> > > + */
> > > +
> > > +#include <dt-bindings/power/xlnx-zynqmp-power.h>
>
> [ ... ]
>
> > > +MODULE_DEVICE_TABLE(of, zynqmp_r5_remoteproc_match);
> > > +
> > > +static struct platform_driver zynqmp_r5_remoteproc_driver = {
> > > + .probe = zynqmp_r5_remoteproc_probe,
> > > + .driver = {
> > > + .name = "zynqmp_r5_remoteproc",
> > > + .of_match_table = zynqmp_r5_remoteproc_match,
> > > + },
> > > +};
> > > +module_platform_driver(zynqmp_r5_remoteproc_driver);
> > > +
> > > +MODULE_DESCRIPTION("Xilinx R5F remote processor driver");
> > > +MODULE_AUTHOR("Xilinx Inc.");
> > > +MODULE_LICENSE("GPL");
> > There is a discrepency between the GPL-2.0 in the SPDS identifier and the above.
>
> Also, changing to MODULE_LICENSE("GPL v2") gives following warning:
>
> WARNING: Prefer "GPL" over "GPL v2" - see commit bf7fbeeae6db ("module: Cure
> the MODULE_LICENSE "GPL" vs. "GPL v2" bogosity")
> #1115: FILE: drivers/remoteproc/xlnx_r5_remoteproc.c:1034:
> +MODULE_LICENSE("GPL v2");
>
> So, It looks like SPDX-License-Identifier should be GPL-2.0-only and
> MODULE_LICENSE should be change to "GPL".
Commit bf7fbeeae6db is an interesting read - thanks for pointing it out.
>
> It this ok? Any other suggestions ?
What you have looks good, in that regard there is no need to change anything
from your patch.
>
> Thanks,
>
> Tanmay
>
> >
> > More comments tomorrow or Tuesday.
> >
> > Thanks,
> > Mathieu
> >
> > > --
> > > 2.25.1
> > >
next prev parent reply other threads:[~2022-09-29 17:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-08 1:39 [PATCH v9 0/6] Add Xilinx RPU subsystem support Tanmay Shah
2022-07-08 1:39 ` [PATCH v9 1/6] dt-bindings: remoteproc: Add Xilinx RPU subsystem bindings Tanmay Shah
2022-09-01 17:38 ` Mathieu Poirier
2022-09-01 19:29 ` Tanmay Shah
2022-09-06 23:02 ` Tanmay Shah
2022-07-08 1:39 ` [PATCH v9 2/6] arm64: dts: xilinx: zynqmp: Add RPU subsystem device node Tanmay Shah
2022-07-08 1:39 ` [PATCH v9 3/6] firmware: xilinx: Add ZynqMP firmware ioctl enums for RPU configuration Tanmay Shah
2022-07-08 1:39 ` [PATCH v9 4/6] firmware: xilinx: Add shutdown/wakeup APIs Tanmay Shah
2022-07-08 1:39 ` [PATCH v9 5/6] firmware: xilinx: Add RPU configuration APIs Tanmay Shah
2022-07-08 1:39 ` [PATCH v9 6/6] drivers: remoteproc: Add Xilinx r5 remoteproc driver Tanmay Shah
2022-07-08 19:38 ` kernel test robot
2022-09-01 20:25 ` Mathieu Poirier
2022-09-02 0:04 ` Tanmay Shah
2022-09-02 19:59 ` Mathieu Poirier
2022-09-08 19:42 ` Tanmay Shah
2022-09-02 0:06 ` Tanmay Shah
2022-09-26 22:02 ` Tanmay Shah
2022-09-29 17:22 ` Mathieu Poirier [this message]
2022-09-29 19:28 ` Tanmay Shah
2022-09-29 23:20 ` Mathieu Poirier
2022-09-06 21:07 ` Mathieu Poirier
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=20220929172200.GB3107608@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=ben.levinsky@xilinx.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=michal.simek@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=tanmay.shah@xilinx.com \
--cc=tanmays@amd.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