All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joe Perches <joe@perches.com>,
	davem@davemloft.net, Philippe Ombredanne <pombredanne@nexb.com>
Cc: 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 10:52:23 -0700	[thread overview]
Message-ID: <1521568343.12746.4.camel@intel.com> (raw)
In-Reply-To: <1521567660.12047.5.camel@perches.com>

[-- Attachment #1: Type: text/plain, Size: 778 bytes --]

On Tue, 2018-03-20 at 10:41 -0700, Joe Perches wrote:
> On Tue, 2018-03-20 at 10:13 -0700, Jeff Kirsher wrote:
> > Add the SPDX identifiers to all the Intel wired LAN driver files,
> > as
> > outlined in Documentation/process/license-rules.rst.
> 
> So far the Documentation does not show using the -only variant.
> 
> For a discussion, please see:
> https://lkml.org/lkml/2018/2/8/311

:-( I had it originally as GPL-2.0 and then it was pointed out that it
was being deprecated, so rather than creating future thrash over the
change, figured I would be ahead of the game.

> 
> > diff --git 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
> 
> etc...

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-03-20 17:51 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 [this message]
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

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=1521568343.12746.4.camel@intel.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=davem@davemloft.net \
    --cc=joe@perches.com \
    --cc=jogreene@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=pombredanne@nexb.com \
    --cc=sassmann@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.