From: Stephen Hemminger <stephen@networkplumber.org>
To: gdawar@solarflare.com
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: [dpdk-dev] [PATCH] net/sfc/base: add missing SPDX license header
Date: Fri, 8 Nov 2019 09:19:37 -0800 [thread overview]
Message-ID: <20191108171937.9813-1-stephen@networkplumber.org> (raw)
The meson.build file is missing the required license header.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
drivers/net/sfc/base/meson.build | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/sfc/base/meson.build b/drivers/net/sfc/base/meson.build
index 6c80305820ce..5fbe24014ec6 100644
--- a/drivers/net/sfc/base/meson.build
+++ b/drivers/net/sfc/base/meson.build
@@ -1,3 +1,5 @@
+# SPDX-License-Identifier: BSD-3-Clause
+#
# Copyright (c) 2016-2018 Solarflare Communications Inc.
# All rights reserved.
#
--
2.20.1
next reply other threads:[~2019-11-08 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 17:19 Stephen Hemminger [this message]
2019-11-08 17:25 ` Ferruh Yigit
2019-11-08 17:27 ` Stephen Hemminger
2019-11-09 18:00 ` Andrew Rybchenko
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=20191108171937.9813-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=gdawar@solarflare.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;
as well as URLs for NNTP newsgroup(s).