public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@sonymobile.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Kumar Gala <galak@codeaurora.org>,
	Andy Gross <agross@codeaurora.org>,
	David Brown <davidb@codeaurora.org>,
	Jeffrey Hugo <jhugo@codeaurora.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-soc@vger.kernel.org" <linux-soc@vger.kernel.org>
Subject: Re: [PATCH 2/2] soc: qcom: Add Shared Memory Manager driver
Date: Fri, 10 Apr 2015 17:30:05 -0700	[thread overview]
Message-ID: <20150411003004.GC12607@sonymobile.com> (raw)
In-Reply-To: <1428146178.7898.75.camel@x220>

On Sat 04 Apr 04:16 PDT 2015, Paul Bolle wrote:

> On Fri, 2015-04-03 at 16:03 -0700, Bjorn Andersson wrote:
> > --- a/drivers/soc/qcom/Kconfig
> > +++ b/drivers/soc/qcom/Kconfig
>  
> > +config QCOM_SMEM
> > +	tristate "Qualcomm Shared Memory Manager (SMEM)"
> > +	depends on ARCH_QCOM
> > +	help
> > +	  Say y here to enable support for the Qualcomm Shared Memory Manager.
> > +	  The driver provides an interface to items in a heap shared among all
> > +	  processors in a Qualcomm platform.
> 
> > --- a/drivers/soc/qcom/Makefile
> > +++ b/drivers/soc/qcom/Makefile
> > @@ -1 +1,2 @@
> 
> > +obj-$(CONFIG_QCOM_SMEM) +=	smem.o
> 
> Just to make absolutely sure I'm not misreading this Makefile: if
> QCOM_SMEM is set to 'm' this will generate the module smem.ko, right?
> 

Right.

> > --- /dev/null
> > +++ b/drivers/soc/qcom/smem.c
> > @@ -0,0 +1,763 @@
> > +/*
> > + * Copyright (c) 2015, Sony Mobile Communications AB.
> > + * Copyright (c) 2012-2013, The Linux Foundation. All rights reserved.
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2 and
> > + * only version 2 as published by the Free Software Foundation.
> > + *
> > + * This program is distributed in the hope that it will be useful,
> > + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> > + * GNU General Public License for more details.
> > + */
> 
> > +MODULE_LICENSE("GPLv2");
> 
> "GPLv2" doesn't indicate a GPL compatible license according to
> include/linux/license.h. Loading smem.ko should trigger a warning and
> taint the kernel. So you want
>     MODULE_LICENSE("GPL v2");
> 
> here. 

Thanks for noticing, I will correct this.

Regards,
Bjorn

  reply	other threads:[~2015-04-11  0:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 23:03 [PATCH 1/2] soc: qcom: Add device tree binding for SMEM Bjorn Andersson
2015-04-03 23:03 ` [PATCH 2/2] soc: qcom: Add Shared Memory Manager driver Bjorn Andersson
2015-04-04 11:16   ` Paul Bolle
2015-04-11  0:30     ` Bjorn Andersson [this message]
2015-04-10 21:30   ` Andy Gross
2015-04-10 23:55     ` Bjorn Andersson
2015-04-11  4:58       ` Andy Gross

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=20150411003004.GC12607@sonymobile.com \
    --to=bjorn.andersson@sonymobile.com \
    --cc=agross@codeaurora.org \
    --cc=davidb@codeaurora.org \
    --cc=galak@codeaurora.org \
    --cc=jhugo@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-soc@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    /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