public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] cpufreq: arm_big_little: fix module license spec
Date: Thu, 7 Aug 2014 17:29:34 +0200	[thread overview]
Message-ID: <20140807152934.GT1933@pengutronix.de> (raw)
In-Reply-To: <mvmiom48knf.fsf@hawking.suse.de>

On Thu, Aug 07, 2014 at 04:00:20PM +0200, Andreas Schwab wrote:
> Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de> writes:
> 
> > Having no license specification in a module taints the kernel during load
> > with:
> >
> > 	arm_big_little: module license 'unspecified' taints kernel.
> >
> > and also the linker doesn't allow it to make use of GPL-exported symbols
> > which in this case also results in errors like:
> >
> > 	arm_big_little: Unknown symbol cpufreq_register_driver (err 0)
> >
> > . The header of the driver specifies a GPL v2 license, so note that
> > accordingly. While at it also add a description and an author and fix
> > the license in a companion file to explicit v2.
> >
> > Reported-by: Andreas Schwab <schwab@suse.de>
> > Signed-off-by: Uwe Kleine-K?nig <u.kleine-koenig@pengutronix.de>
> > ---
> >  drivers/cpufreq/arm_big_little.c    | 4 ++++
> >  drivers/cpufreq/arm_big_little_dt.c | 2 +-
> >  2 files changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/cpufreq/arm_big_little.c b/drivers/cpufreq/arm_big_little.c
> > index 1f4d4e315057..b600f3107bef 100644
> > --- a/drivers/cpufreq/arm_big_little.c
> > +++ b/drivers/cpufreq/arm_big_little.c
> > @@ -593,3 +593,7 @@ void bL_cpufreq_unregister(struct cpufreq_arm_bL_ops *ops)
> >  	arm_bL_ops = NULL;
> >  }
> >  EXPORT_SYMBOL_GPL(bL_cpufreq_unregister);
> > +
> > +MODULE_AUTHOR("Viresh Kumar <viresh.kumar@linaro.org>");
> > +MODULE_DESCRIPTION("Generic ARM big LITTLE cpufreq driver");
> > +MODULE_LICENSE("GPL v2");
> 
> drivers/cpufreq/arm_big_little.c:613:15: error: expected declaration specifiers or ?...? before string constant
>  MODULE_AUTHOR("Viresh Kumar <viresh.kumar@linaro.org>");
>                ^
> drivers/cpufreq/arm_big_little.c:614:20: error: expected declaration specifiers or ?...? before string constant
>  MODULE_DESCRIPTION("Generic ARM big LITTLE cpufreq driver");
>                     ^
> drivers/cpufreq/arm_big_little.c:615:16: error: expected declaration specifiers or ?...? before string constant
>  MODULE_LICENSE("GPL v2");
>                 ^
> 
Does adding

	#include <linux/module.h>

in that file fix the problem?

Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2014-08-07 15:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-31  7:18 Missing module license in arm_big_little Andreas Schwab
2014-07-31  7:36 ` [PATCH] cpufreq: arm_big_little: fix module license spec Uwe Kleine-König
2014-08-01  9:22   ` Viresh Kumar
2014-08-07 14:00   ` Andreas Schwab
2014-08-07 15:29     ` Uwe Kleine-König [this message]
2014-08-07 15:33       ` Andreas Schwab

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=20140807152934.GT1933@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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