From: kys@linuxonhyperv.comi
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
devel@linuxdriverproject.org, olaf@aepfle.de, apw@canonical.com,
vkuznets@redhat.com, jasowang@redhat.com,
leann.ogasawara@canonical.com, marcelo.cerri@canonical.com,
sthemmin@microsoft.com
Subject: [PATCH 3/4] hv: add SPDX license to trace
Date: Tue, 27 Mar 2018 15:01:03 -0700 [thread overview]
Message-ID: <20180327220104.19700-3-kys@linuxonhyperv.comi> (raw)
In-Reply-To: <20180327220104.19700-1-kys@linuxonhyperv.comi>
From: Stephen Hemminger <stephen@networkplumber.org>
Missing license on Hyper-V VMBUS tracing files.
Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
---
drivers/hv/hv_trace.c | 2 ++
drivers/hv/hv_trace.h | 2 ++
2 files changed, 4 insertions(+)
diff --git a/drivers/hv/hv_trace.c b/drivers/hv/hv_trace.c
index df47acd01a81..38d359cf1e70 100644
--- a/drivers/hv/hv_trace.c
+++ b/drivers/hv/hv_trace.c
@@ -1,3 +1,5 @@
+// SPDX-License-Identifier: GPL-2.0
+
#include "hyperv_vmbus.h"
#define CREATE_TRACE_POINTS
diff --git a/drivers/hv/hv_trace.h b/drivers/hv/hv_trace.h
index d635ee95b20d..999f80a63bff 100644
--- a/drivers/hv/hv_trace.h
+++ b/drivers/hv/hv_trace.h
@@ -1,3 +1,5 @@
+// SPDX-License-Identifier: GPL-2.0
+
#undef TRACE_SYSTEM
#define TRACE_SYSTEM hyperv
--
2.15.1
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-03-27 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 21:58 [PATCH 0/4] Drivers: hv: vmbus: Miscellaneous fixes kys
2018-03-27 22:01 ` [PATCH 1/4] Drivers: hv: vmbus: respect what we get from hv_get_synint_state() kys
2018-03-27 22:01 ` [PATCH 2/4] Drivers: hv: vmbus: do not mark HV_PCIE as perf_device kys
2018-03-27 22:01 ` kys [this message]
2018-03-27 22:01 ` [PATCH 4/4] hv: add SPDX license id to Kconfig kys
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=20180327220104.19700-3-kys@linuxonhyperv.comi \
--to=kys@linuxonhyperv.comi \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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.