From: Tom Hromatka <tom.hromatka@oracle.com>
To: "Shuah Khan (Samsung OSG)" <shuah@kernel.org>,
gregkh@linuxfoundation.org, allen.pais@oracle.com,
davem@davemloft.net
Cc: linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests: sparc64: Add missing SPDX License Identifiers
Date: Thu, 14 Jun 2018 12:49:08 -0600 [thread overview]
Message-ID: <2f9d0d78-067f-7a25-dc10-f4476a7ae54c@oracle.com> (raw)
In-Reply-To: <20180614010559.5144-1-shuah@kernel.org>
On 06/13/2018 07:05 PM, Shuah Khan (Samsung OSG) wrote:
> Add missing SPDX License Identifiers to Makefile(s).
>
> Signed-off-by: Shuah Khan (Samsung OSG) <shuah@kernel.org>
Reviewed-by: Tom Hromatka <tom.hromatka@oracle.com>
> ---
> tools/testing/selftests/sparc64/Makefile | 1 +
> tools/testing/selftests/sparc64/drivers/Makefile | 2 +-
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/sparc64/Makefile b/tools/testing/selftests/sparc64/Makefile
> index 76b2206932c3..a19531dba4dc 100644
> --- a/tools/testing/selftests/sparc64/Makefile
> +++ b/tools/testing/selftests/sparc64/Makefile
> @@ -1,3 +1,4 @@
> +# SPDX-License-Identifier: GPL-2.0
> uname_M := $(shell uname -m 2>/dev/null || echo not)
> ARCH ?= $(shell echo $(uname_M) | sed -e s/x86_64/x86/)
>
> diff --git a/tools/testing/selftests/sparc64/drivers/Makefile b/tools/testing/selftests/sparc64/drivers/Makefile
> index 6264f40bbdbc..deb0df415565 100644
> --- a/tools/testing/selftests/sparc64/drivers/Makefile
> +++ b/tools/testing/selftests/sparc64/drivers/Makefile
> @@ -1,4 +1,4 @@
> -
> +# SPDX-License-Identifier: GPL-2.0
> INCLUDEDIR := -I.
> CFLAGS := $(CFLAGS) $(INCLUDEDIR) -Wall -O2 -g
>
prev parent reply other threads:[~2018-06-14 18:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 1:05 Shuah Khan (Samsung OSG)
2018-06-14 18:49 ` Tom Hromatka [this message]
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=2f9d0d78-067f-7a25-dc10-f4476a7ae54c@oracle.com \
--to=tom.hromatka@oracle.com \
--cc=allen.pais@oracle.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@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
all inboxes | Powered by JetHome®