From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Suma Hegde <Suma.Hegde@amd.com>, Hans de Goede <hdegoede@redhat.com>
Cc: platform-driver-x86@vger.kernel.org,
Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>
Subject: Re: [v6 08/10] platform/x86/amd/hsmp: Create mutually exclusive ACPI and plat drivers
Date: Thu, 29 Aug 2024 14:31:24 +0300 (EEST) [thread overview]
Message-ID: <66fd6c95-7a16-b9f5-6efd-232c947ac514@linux.intel.com> (raw)
In-Reply-To: <1b183743-1b78-41cc-a121-1fa6345fa397@amd.com>
[-- Attachment #1: Type: text/plain, Size: 2334 bytes --]
On Thu, 29 Aug 2024, Suma Hegde wrote:
> On 8/29/2024 3:55 PM, Ilpo Järvinen wrote:
> >
> > On Thu, 29 Aug 2024, Suma Hegde wrote:
> >
> > > Separate the probes for HSMP ACPI and platform device drivers.
> > >
> > > Provide a Kconfig option to choose between
> > > ACPI or the platform device based driver.
> > > The common code which is the core part of the HSMP driver
> > > maintained at hsmp.c is guarded by AMD_HSMP config and is selected by
> > > these two driver configs.
> > >
> > > Also add "|| COMPILE_TEST" clause in Kconfig to get build coverage
> > > for HSMP.
> > >
> > > Signed-off-by: Suma Hegde <suma.hegde@amd.com>
> > > Reviewed-by: Naveen Krishna Chatradhi <naveenkrishna.chatradhi@amd.com>
> > > ---
> > > Changes since v5:
> > > 1. Update documentation to reduce line length, update SPDK line and update
> > > the wordings.
> > > 2. Change module license from GPL v2 to GPL and update SPDX license line
> > > in plat.c and acpi.c.
> > Hi Suma,
> >
> > Just to be sure you're not doing the SPDX license line change because of
> > what I said, the change in MODULE_LICENSE() from "GPL v2" -> "GPL" by no
> > means implies SPDX license has to be changed from "GPL-2.0" to
> > "GPL-2.0-or-later".
> >
> > I'm sorry about the confusion I might have caused.
> >
> > If I've understood correctly, MODULE_LICENSE()'s value is mainly used to
> > determine eg. which exports (if the _GPL EXPORTs can be used) can be
> > used and taint flags, and that does not require knowing exact GPL version
> > so it was simplified to "GPL" long time ago w/o requirement to change the
> > oldones (to avoid unnecessary churn).
>
> I wanted to update the license to "GPL-2.0-or-later" instead of "GPL-2.0",
> that's the main reason I modified SPDX line.
>
> But I missed to update the license for hsmp.h and hsmp.c files. I will send v7
> with this change and addressing other comments.
>
> Kindly respond me if the SPDX license update has to be made as a separate
> patch.
>
> Thank you.
I've never really come across patches that attempt change the license of a
file (I haven't been around as a maintainer that long). The obvious
problem here is that you're not the sole contributor to this code.
Hans, have you come across this kind of case before?
--
i.
next prev parent reply other threads:[~2024-08-29 11:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 6:05 [v6 01/10] platform/x86/amd/hsmp: Create hsmp/ directory Suma Hegde
2024-08-29 6:05 ` [v6 02/10] platform/x86/amd/hsmp: Create wrapper function init_acpi() Suma Hegde
2024-08-29 6:06 ` [v6 03/10] platform/x86/amd/hsmp: Convert amd_hsmp_rdwr() to a function pointer Suma Hegde
2024-08-29 6:06 ` [v6 04/10] platform/x86/amd/hsmp: Move structure and macros to header file Suma Hegde
2024-08-29 6:06 ` [v6 05/10] platform/x86/amd/hsmp: Move platform device specific code to plat.c Suma Hegde
2024-08-29 6:06 ` [v6 06/10] platform/x86/amd/hsmp: Move ACPI code to acpi.c Suma Hegde
2024-08-29 6:06 ` [v6 07/10] platform/x86/amd/hsmp: Change generic plat_dev name to hsmp_pdev Suma Hegde
2024-08-29 6:06 ` [v6 08/10] platform/x86/amd/hsmp: Create mutually exclusive ACPI and plat drivers Suma Hegde
2024-08-29 10:25 ` Ilpo Järvinen
2024-08-29 11:12 ` Suma Hegde
2024-08-29 11:31 ` Ilpo Järvinen [this message]
2024-08-29 6:06 ` [v6 09/10] platform/x86/amd/hsmp: Use name space while exporting module symbols Suma Hegde
2024-08-29 6:06 ` [v6 10/10] platform/x86/amd/hsmp: Use dev_groups in the driver structure Suma Hegde
2024-08-29 10:47 ` Ilpo Järvinen
2024-08-29 6:06 ` [v6 01/10] platform/x86/amd/hsmp: Create hsmp/ directory Suma Hegde
2024-08-29 6:06 ` [v6 02/10] platform/x86/amd/hsmp: Create wrapper function init_acpi() Suma Hegde
2024-08-29 6:06 ` [v6 03/10] platform/x86/amd/hsmp: Convert amd_hsmp_rdwr() to a function pointer Suma Hegde
2024-08-29 6:06 ` [v6 04/10] platform/x86/amd/hsmp: Move structure and macros to header file Suma Hegde
2024-08-29 6:06 ` [v6 05/10] platform/x86/amd/hsmp: Move platform device specific code to plat.c Suma Hegde
2024-08-29 6:06 ` [v6 06/10] platform/x86/amd/hsmp: Move ACPI code to acpi.c Suma Hegde
2024-08-29 6:06 ` [v6 07/10] platform/x86/amd/hsmp: Change generic plat_dev name to hsmp_pdev Suma Hegde
2024-08-29 6:06 ` [v6 08/10] platform/x86/amd/hsmp: Create mutually exclusive ACPI and plat drivers Suma Hegde
2024-08-29 6:06 ` [v6 09/10] platform/x86/amd/hsmp: Use name space while exporting module symbols Suma Hegde
2024-08-29 6:06 ` [v6 10/10] platform/x86/amd/hsmp: Use dev_groups in the driver structure Suma Hegde
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=66fd6c95-7a16-b9f5-6efd-232c947ac514@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Suma.Hegde@amd.com \
--cc=hdegoede@redhat.com \
--cc=naveenkrishna.chatradhi@amd.com \
--cc=platform-driver-x86@vger.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