public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
	Teddy Wang <teddy.wang@siliconmotion.com>,
	gzhou1 <guojian.zhou@windriver.com>
Subject: Re: [PATCH] staging: sm750fb: update license
Date: Sat, 26 Nov 2016 12:02:45 +0100	[thread overview]
Message-ID: <20161126110245.GA8388@kroah.com> (raw)
In-Reply-To: <1480151262-5183-1-git-send-email-sudipm.mukherjee@gmail.com>

On Sat, Nov 26, 2016 at 09:07:42AM +0000, Sudip Mukherjee wrote:
> The driver was actually released with BSD license. It also gained GPL
> when it was submitted to be included in the kernel.
> 
> Cc: Teddy Wang <teddy.wang@siliconmotion.com>
> Cc: gzhou1 <guojian.zhou@windriver.com> 
> Signed-off-by: Sudip Mukherjee <sudip.mukherjee@codethink.co.uk>
> ---
>  drivers/staging/sm750fb/sm750.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/staging/sm750fb/sm750.c b/drivers/staging/sm750fb/sm750.c
> index 2d22c51..e9632f1 100644
> --- a/drivers/staging/sm750fb/sm750.c
> +++ b/drivers/staging/sm750fb/sm750.c
> @@ -1243,4 +1243,4 @@ static void __exit lynxfb_exit(void)
>  MODULE_AUTHOR("monk liu <monk.liu@siliconmotion.com>");
>  MODULE_AUTHOR("Sudip Mukherjee <sudip@vectorindia.org>");
>  MODULE_DESCRIPTION("Frame buffer driver for SM750 chipset");
> -MODULE_LICENSE("GPL v2");
> +MODULE_LICENSE("Dual BSD/GPL");

Should you also update the top of the files that don't say anything
about licenses?

I'll take this patch, but an update for them would also be good.

thanks,

greg k-h

  reply	other threads:[~2016-11-26 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-26  9:07 [PATCH] staging: sm750fb: update license Sudip Mukherjee
2016-11-26 11:02 ` Greg Kroah-Hartman [this message]
2016-12-08 22:20   ` Sudip Mukherjee

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=20161126110245.GA8388@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=guojian.zhou@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=teddy.wang@siliconmotion.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