From: Jeff Kirsher <jeffrey.t.kirsher@intel•com>
To: Stephen Hemminger <stephen@networkplumber•org>
Cc: davem@davemloft•net, netdev@vger•kernel.org, nhorman@redhat•com,
sassmann@redhat•com, jogreene@redhat•com
Subject: Re: [net-next] intel: add SPDX identifiers to all the Intel drivers
Date: Tue, 20 Mar 2018 17:59:27 -0700 [thread overview]
Message-ID: <1521593967.15055.1.camel@intel.com> (raw)
In-Reply-To: <20180320174718.130cc253@xeon-e3>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
On Tue, 2018-03-20 at 17:47 -0700, Stephen Hemminger wrote:
> On Tue, 20 Mar 2018 10:13:20 -0700
> Jeff Kirsher <jeffrey.t.kirsher@intel•com> wrote:
>
> > diff --git a/drivers/net/ethernet/intel/e100.c
> > b/drivers/net/ethernet/intel/e100.c
> > index 29486478836e..a750a5fe373a 100644
> > --- a/drivers/net/ethernet/intel/e100.c
> > +++ b/drivers/net/ethernet/intel/e100.c
> > @@ -1,3 +1,4 @@
> > +// SPDX-License-Identifier: GPL-2.0-only
> >
> > /**********************************************************************
> > *********
> >
> > Intel PRO/100 Linux driver
>
> SPDX makes things easier but I thought the advantage of SPDX
> was getting rid of the boilerplate! Can you convince the lawyers
> to drop the GPL boilerplate comment please.
>
> It has already been done on other projects.
Its in the works. Just waiting to hear back from the lawyers that it is ok
to remove the boiler plate headers, before I generate a patch to clean up
the Intel drivers.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-03-21 0:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 17:13 [net-next] intel: add SPDX identifiers to all the Intel drivers Jeff Kirsher
2018-03-20 17:41 ` Joe Perches
2018-03-20 17:52 ` Jeff Kirsher
2018-03-20 20:48 ` Allan, Bruce W
2018-03-20 21:01 ` Joe Perches
2018-03-20 23:46 ` Philippe Ombredanne
2018-03-21 1:09 ` Jeff Kirsher
2018-03-21 1:14 ` Joe Perches
2018-03-21 9:38 ` Greg Kroah-Hartman
2018-03-21 0:47 ` Stephen Hemminger
2018-03-21 0:59 ` Jeff Kirsher [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=1521593967.15055.1.camel@intel.com \
--to=jeffrey.t.kirsher@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=jogreene@redhat$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhorman@redhat$(echo .)com \
--cc=sassmann@redhat$(echo .)com \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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