mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ira Weiny <ira.weiny@intel.com>
To: <nifan.cxl@gmail.com>, <dave.jiang@intel.com>,
	<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
	<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
	<Jonathan.Cameron@huawei.com>
Cc: <linux-cxl@vger.kernel.org>, <a.manzanares@samsung.com>,
	<dave@stgolabs.net>, <linux-kernel@vger.kernel.org>,
	<nifan.cxl@gmail.com>, Fan Ni <fan.ni@samsung.com>
Subject: Re: [PATCH] cxl/region: Add module license declaration to cxl region module source code
Date: Tue, 21 May 2024 10:25:58 -0500	[thread overview]
Message-ID: <664cbd06b5342_364af29491@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20240520193106.994172-1-nifan.cxl@gmail.com>

nifan.cxl@ wrote:
> From: Fan Ni <fan.ni@samsung.com>
> 
> This change explicitly specifies the licensing terms for the CXL region
> module as GPL v2. This commit does not introduce any functional changes
> to the behavior or functionality of the CXL region module.
> It solely adds the MODULE_LICENSE declaration to the module source file.

Why is this needed?  The region code is added to cxl_core when built and
that module already reports the correct module license.

10:24:55 > modinfo cxl_core | grep lic
license:        GPL v2

Ira

> 
> Signed-off-by: Fan Ni <fan.ni@samsung.com>
> ---
>  drivers/cxl/core/region.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> index 5c186e0a39b9..e299ddcbd1a2 100644
> --- a/drivers/cxl/core/region.c
> +++ b/drivers/cxl/core/region.c
> @@ -3204,3 +3204,4 @@ void cxl_region_exit(void)
>  MODULE_IMPORT_NS(CXL);
>  MODULE_IMPORT_NS(DEVMEM);
>  MODULE_ALIAS_CXL(CXL_DEVICE_REGION);
> +MODULE_LICENSE("GPL v2");
> -- 
> 2.43.0
> 



  reply	other threads:[~2024-05-21 15:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 19:29 nifan.cxl
2024-05-21 15:25 ` Ira Weiny [this message]
2024-05-21 16:35   ` Dan Williams

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=664cbd06b5342_364af29491@iweiny-mobl.notmuch \
    --to=ira.weiny@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=a.manzanares@samsung.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=fan.ni@samsung.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nifan.cxl@gmail.com \
    --cc=vishal.l.verma@intel.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

all inboxes | Powered by JetHome®