linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor@chromium.org>
To: Grant Grundler <grundler@google.com>
Cc: linux-input <linux-input@vger.kernel.org>,
	Dmitry Torokhov <dtor@chromium.org>
Subject: Re: Remove DRIVER_LICENSE?
Date: Wed, 4 Jan 2017 10:12:20 -0800	[thread overview]
Message-ID: <CAE_wzQ975aiGGdF78bXxqOTNFg-p3HUOsxicq_a1OS8NcdJROw@mail.gmail.com> (raw)
In-Reply-To: <CANEJEGvTnSk5kU7LKVLBS73hLM1a_oTKj8tBegFWa+S2MCLpJw@mail.gmail.com>

On Wed, Jan 4, 2017 at 9:58 AM, Grant Grundler <grundler@google.com> wrote:
> I'm researching MODULE_LICENSE uses/declarations and AFAICT
> DRIVER_LICENSE is only obfuscating the programatically declared
> license. e.g.:
>
> drivers/hid/hid-core.c:#define DRIVER_LICENSE "GPL"
> drivers/hid/hid-core.c:MODULE_LICENSE(DRIVER_LICENSE);
> drivers/hid/usbhid/usbmouse.c:#define DRIVER_LICENSE "GPL"
> drivers/hid/usbhid/usbmouse.c:MODULE_LICENSE(DRIVER_LICENSE);
> drivers/hid/usbhid/usbkbd.c:#define DRIVER_LICENSE "GPL"
> drivers/hid/usbhid/usbkbd.c:MODULE_LICENSE(DRIVER_LICENSE);
> drivers/hid/wacom.h:#define DRIVER_LICENSE "GPL"
> drivers/hid/wacom_sys.c:MODULE_LICENSE(DRIVER_LICENSE);
>
> Any objection to removing those uses in drivers/hid?

Sounds good to me.

Thanks.

-- 
Dmitry

  reply	other threads:[~2017-01-04 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-04 17:58 Remove DRIVER_LICENSE? Grant Grundler
2017-01-04 18:12 ` Dmitry Torokhov [this message]
2017-01-04 18:14   ` Dmitry Torokhov
2017-01-05  9:24     ` Benjamin Tissoires
2017-01-05 10:19     ` Jiri Kosina
2017-01-05 17:29       ` Grant Grundler
2017-01-05 19:09       ` Grant Grundler

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=CAE_wzQ975aiGGdF78bXxqOTNFg-p3HUOsxicq_a1OS8NcdJROw@mail.gmail.com \
    --to=dtor@chromium.org \
    --cc=grundler@google.com \
    --cc=linux-input@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).