From: "Dirk Hohndel (VMware)" <dirk@hohndel.org>
To: dri-devel@lists.freedesktop.org
Cc: "Thomas Hellstrom" <thellstrom@vmware.com>,
"Christian König" <christian.koenig@amd.com>
Subject: drm SPDX updates
Date: Fri, 4 May 2018 00:15:09 +0200 [thread overview]
Message-ID: <20180503221517.58682-1-dirk@hohndel.org> (raw)
This series clarifies licenses, removes unnecessary boilerplate and addas
SPDX headers for files in drm that are copyrighted by VMware.
/D
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-05-03 22:16 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 22:15 Dirk Hohndel (VMware) [this message]
2018-05-03 22:15 ` [PATCH 1/8] drm: add SPDX idenitifier and clarify license Dirk Hohndel (VMware)
2018-05-03 22:15 ` [PATCH 2/8] drm/amd: Add SPDX identifier " Dirk Hohndel (VMware)
2018-05-03 22:15 ` [PATCH 3/8] drm: " Dirk Hohndel (VMware)
2018-05-03 22:15 ` [PATCH 4/8] drm/noveau: " Dirk Hohndel (VMware)
2018-05-03 22:15 ` [PATCH 5/8] drm/radeon: " Dirk Hohndel (VMware)
2018-05-03 22:15 ` [PATCH 6/8] drm/ttm: add SPDX idenitifier " Dirk Hohndel (VMware)
2018-05-03 22:15 ` [PATCH 7/8] drm/vmwgfx: " Dirk Hohndel (VMware)
2018-05-03 22:15 ` [PATCH 8/8] " Dirk Hohndel (VMware)
2018-05-04 6:18 ` [PATCH 7/8] " Thomas Hellstrom
2018-05-04 6:41 ` Dirk Hohndel
2018-05-04 7:39 ` Thomas Hellstrom
2018-05-06 23:16 drm SPDX updates Dirk Hohndel (VMware)
2018-05-14 5:59 ` Thomas Gleixner
2018-05-14 14:54 ` Dirk Hohndel
2018-05-14 15:01 ` Thomas Hellstrom
2018-05-14 15:10 ` Dirk Hohndel
2018-05-14 16:31 ` Daniel Vetter
2018-05-15 19:53 ` Alex Deucher
2018-06-29 19:32 ` Alex Deucher
2018-06-29 19:36 ` Dirk Hohndel
2018-06-29 19:39 ` Alex Deucher
2018-06-29 19:46 ` Dirk Hohndel
2018-06-29 20:32 ` Alex Deucher
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=20180503221517.58682-1-dirk@hohndel.org \
--to=dirk@hohndel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thellstrom@vmware.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 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.