linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Zhipeng Wang <zhipeng.wang_1@nxp.com>
Cc: rafael@kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] cpufreq: dt-platdev: Add MODULE_LICENSE
Date: Fri, 2 Jun 2023 09:42:34 +0530	[thread overview]
Message-ID: <20230602041234.sb77clozdjqorz3j@vireshk-i7> (raw)
In-Reply-To: <20230524153417.2738448-1-zhipeng.wang_1@nxp.com>

On 24-05-23, 15:34, Zhipeng Wang wrote:
> Add MODULE_LICENSE to support building as module.
> 
> Signed-off-by: Zhipeng Wang <zhipeng.wang_1@nxp.com>
> ---
>  drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
> index 338cf6cc6596..54529aa16d53 100644
> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
> @@ -214,3 +214,4 @@ static int __init cpufreq_dt_platdev_init(void)
>  			       sizeof(struct cpufreq_dt_platform_data)));
>  }
>  core_initcall(cpufreq_dt_platdev_init);
> +MODULE_LICENSE("GPL");

Merged both patches and applied. Thanks.

-- 
viresh

      parent reply	other threads:[~2023-06-02  4:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24 15:34 [PATCH 1/2] cpufreq: dt-platdev: Add MODULE_LICENSE Zhipeng Wang
2023-05-24 10:45 ` Viresh Kumar
2023-05-24 11:32   ` [EXT] " Zhipeng Wang
2023-05-24 15:34 ` [PATCH 2/2] cpufreq: dt-platdev: Support building cpufreq platdev driver as module Zhipeng Wang
2023-08-29 18:00   ` Aurelien Jarno
2023-08-30  3:09     ` [EXT] " Zhipeng Wang
2023-08-30  5:08       ` Aurelien Jarno
2023-08-31 10:50         ` Viresh Kumar
2023-06-02  4:12 ` Viresh Kumar [this message]

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=20230602041234.sb77clozdjqorz3j@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=zhipeng.wang_1@nxp.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;
as well as URLs for NNTP newsgroup(s).