All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: clemens@ladisch.de, tiwai@suse.de
Cc: alsa-devel@alsa-project.org
Subject: [PATCH 0/2] ALSA: firewire: use 'GPL' string for module license
Date: Sun, 11 Jun 2023 23:44:43 +0900	[thread overview]
Message-ID: <20230611144445.221529-1-o-takashi@sakamocchi.jp> (raw)

Hi,

Nowadays, the use of "GPL" string in MODULE_LICENSE macro seems to
obsolete "GPL v2" string. This series includes two patches to use it for
modules in ALSA firewire stack contributed by two developers.

This change does not pose any issue for modules contributed by Takashi
Sakamoto, the author of this series, while it is advisable to have careful
consideration for modules contributed by Clemens Ladisch, since the code
related to license will be modified by a developer who is not the
copyright holder.

A commit bf7fbeeae6db ("module: Cure the MODULE_LICENSE "GPL" vs.
"GPL v2" bogosity") adds detail documentation about the macro itself and
clarifies the difference between "GPL" and "GPL v2". The macro is designed
to provide sufficient information to kernel module loader and user space
tools. Both strings have the same meanings, but the latter is legacy.

In conclusion, any change made to the usage of the macro neither result in
significant alterations to license nor copyright.

Takashi Sakamoto (2):
  ALSA: firewire: use 'GPL' string for module license contributed by
    Takashi Sakamoto
  ALSA: firewire: use 'GPL' string for module license contributed by
    Clemens Ladisch

 sound/firewire/bebob/bebob.c         | 2 +-
 sound/firewire/dice/dice.c           | 2 +-
 sound/firewire/digi00x/digi00x.c     | 2 +-
 sound/firewire/fireface/ff.c         | 2 +-
 sound/firewire/fireworks/fireworks.c | 2 +-
 sound/firewire/isight.c              | 2 +-
 sound/firewire/lib.c                 | 2 +-
 sound/firewire/motu/motu.c           | 2 +-
 sound/firewire/oxfw/oxfw.c           | 2 +-
 sound/firewire/tascam/tascam.c       | 2 +-
 10 files changed, 10 insertions(+), 10 deletions(-)

-- 
2.39.2


             reply	other threads:[~2023-06-11 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 14:44 Takashi Sakamoto [this message]
2023-06-11 14:44 ` [PATCH 1/2] ALSA: firewire: use 'GPL' string for module license contributed by Takashi Sakamoto Takashi Sakamoto
2023-06-11 14:44 ` [PATCH 2/2] ALSA: firewire: use 'GPL' string for module license contributed by Clemens Ladisch Takashi Sakamoto
2023-06-12 12:39 ` [PATCH 0/2] ALSA: firewire: use 'GPL' string for module license Takashi Iwai

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=20230611144445.221529-1-o-takashi@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.