From: Anatolij Gustschin <agust@denx.de>
To: capetry.dev@gmail.com
Cc: atull@kernel.org, mdf@kernel.org, linux-fpga@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] fpga: altera-cvp: Insert SPDX-License-Identifier
Date: Tue, 13 Nov 2018 00:08:23 +0100 [thread overview]
Message-ID: <20181113000823.04df5a7a@crub> (raw)
In-Reply-To: <20181108011312.29587-2-capetry.dev@gmail.com>
On Wed, 7 Nov 2018 23:13:11 -0200
capetry.dev@gmail.com capetry.dev@gmail.com wrote:
...
>diff --git a/drivers/fpga/altera-cvp.c b/drivers/fpga/altera-cvp.c
>index 610a1558e..45b7c8c0b 100644
>--- a/drivers/fpga/altera-cvp.c
>+++ b/drivers/fpga/altera-cvp.c
>@@ -1,3 +1,4 @@
>+// SPDX-License-Identifier: GPL-2.0
when SPDX identifier is in place, shouldn't the GPL boilerplate below
be removed?
Anatolij
next prev parent reply other threads:[~2018-11-12 23:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 1:13 [PATCH 0/2] fpga: altera-cvp: clean checkpatch faults capetry.dev
2018-11-08 1:13 ` [PATCH 1/2] fpga: altera-cvp: Insert SPDX-License-Identifier capetry.dev
2018-11-12 23:08 ` Anatolij Gustschin [this message]
2018-11-08 1:13 ` [PATCH 2/2] fpga: altera-cvp: Fix function definition argument capetry.dev
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=20181113000823.04df5a7a@crub \
--to=agust@denx.de \
--cc=atull@kernel.org \
--cc=capetry.dev@gmail.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@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;
as well as URLs for NNTP newsgroup(s).