From: Dirk Hohndel <dirk@hohndel.org>
To: Thomas Gleixner <tglx@tglx.de>
Cc: "Thomas Hellstrom" <thellstrom@vmware.com>,
"Christian König" <christian.koenig@amd.com>,
dri-devel@lists.freedesktop.org
Subject: Re: drm SPDX updates
Date: Mon, 14 May 2018 07:54:31 -0700 [thread overview]
Message-ID: <20180514145431.GL1309@rrmbpvm.gr8dns.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1805140759120.1413@nanos.tec.linutronix.de>
On Mon, May 14, 2018 at 07:59:56AM +0200, Thomas Gleixner wrote:
> Dirk,
>
> On Mon, 7 May 2018, Dirk Hohndel (VMware) wrote:
>
> > License clarifications and SPDX headers for a bunch of files which were
> > authored by VMware.
> >
> > This should address the comments made on the previous series.
> > I added Thomas as Cc (sorry, forgot on the first version) and added a
> > couple of SOBs that I had received in the meantime.
>
> Thanks for cleaning that up.
>
> FWIW: Acked-by: Thomas Gleixner <tglx@linutronix.de>
I haven't seen any comments in the week since I wrote this. I'm not
familiar with the process for the drm changes - so what are the usual next
steps? Do I need to submit all or part of this somewhere else? Or does
Dave simply take the series (since it has no executable code changes at
all)?
/D
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-14 14:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 23:16 drm SPDX updates Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 1/8] drm: add SPDX idenitifier and clarify license Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 2/8] drm/amd: add SPDX identifier " Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 3/8] drm: " Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 4/8] drm/noveau: " Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 5/8] drm/radeon: " Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 6/8] drm/ttm: add SPDX idenitifier " Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 7/8] drm/vmwgfx: " Dirk Hohndel (VMware)
2018-05-06 23:16 ` [PATCH v2 8/8] " Dirk Hohndel (VMware)
2018-05-07 14:50 ` [PATCH v2 7/8] " Thomas Hellstrom
2018-05-07 17:23 ` Dirk Hohndel
2018-05-08 9:57 ` Emil Velikov
2018-05-09 5:31 ` Dirk Hohndel
2018-05-14 5:59 ` drm SPDX updates Thomas Gleixner
2018-05-14 14:54 ` Dirk Hohndel [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2018-05-03 22:15 Dirk Hohndel (VMware)
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=20180514145431.GL1309@rrmbpvm.gr8dns.org \
--to=dirk@hohndel.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=tglx@tglx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox