From: Thomas Gleixner <tglx@linutronix.de>
To: Dave Jones <davej@redhat.com>
Cc: linux-spdx@vger.kernel.org
Subject: list_debug, pcmcia: License cleanup
Date: Sun, 22 May 2022 17:04:41 +0200 (CEST) [thread overview]
Message-ID: <165322121191.3770149.399639028538521068.tglx@xen13> (raw)
Message-ID: <20220522150441.z5N7X-3LW_NBVHnxR39j0H8GM1-pmR0Jeg2lkElCRCw@z> (raw)
Dave!
As you might know we are working on cleaning up the licensing mess in the
kernel and convert it to SPDX license identifiers as the only source of
license information.
Archaeology found unspecific GPL license references, which have been
authored by you.
1) released under the general public license (gpl)
lib/list_debug.c
2) this code is released under the gnu general public license (gpl) this
software is provided as is and any express or implied warranties
including but not limited to the implied warranties of merchantability
and fitness for a particular purpose are disclaimed in no event shall
the author be liable for any direct indirect incidental special
exemplary or consequential damages (including but not limited to
procurement of substitute goods or services loss of use data or profits
or business interruption) however caused and on any theory of liability
whether in contract strict liability or tort (including negligence or
otherwise) arising in any way out of the use of this software even if
advised of the possibility of such damage
drivers/char/pcmcia/synclink_cs.c
https://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git/commit/?id=61e17e546cebe
Can you please either send cleanup patches for the affected files or
indicate which GPLv2 variant you had in mind and I run it through my
cleanup machinery.
Thanks,
Thomas
next reply other threads:[~2022-05-22 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 14:54 Thomas Gleixner [this message]
2022-05-22 15:04 ` list_debug, pcmcia: License cleanup Thomas Gleixner
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=165322121191.3770149.399639028538521068.tglx@xen13 \
--to=tglx@linutronix.de \
--cc=davej@redhat.com \
--cc=linux-spdx@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).