All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: Philippe Ombredanne <pombredanne@nexb.com>,
	"Allan, Bruce W" <bruce.w.allan@intel.com>,
	Joe Perches <joe@perches.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"nhorman@redhat.com" <nhorman@redhat.com>,
	"sassmann@redhat.com" <sassmann@redhat.com>,
	"jogreene@redhat.com" <jogreene@redhat.com>,
	Kate Stewart <kstewart@linuxfoundation.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [net-next] intel: add SPDX identifiers to all the Intel drivers
Date: Wed, 21 Mar 2018 10:38:49 +0100	[thread overview]
Message-ID: <20180321093848.GV14085@kroah.com> (raw)
In-Reply-To: <1521594560.15055.10.camel@intel.com>

On Tue, Mar 20, 2018 at 06:09:20PM -0700, Jeff Kirsher wrote:
> > When the kernel maintainers decide to switch to V3.0 of the SPDX list,
> > the doc will be updated and then Joe's script could be applied at once
> > to update the past.
> 
> I am fine with changing my patch back to v2.6 SPDX ids, as long as Joe's
> script in the future won't touch the Intel wired LAN drivers, since we need
> to retain copyright on several files through out our drivers.

Changing SPDX comment lines should never change the "copyright" of a
file.  If you have questions about stuff like that, please talk to your
corporate lawyers, they will be glad to talk to you all about what
defines "copyright" :)

thanks,

greg "I talk to too many lawyers..." k-h

  parent reply	other threads:[~2018-03-21  9:38 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 [this message]
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=20180321093848.GV14085@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bruce.w.allan@intel.com \
    --cc=davem@davemloft.net \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=joe@perches.com \
    --cc=jogreene@redhat.com \
    --cc=kstewart@linuxfoundation.org \
    --cc=netdev@vger.kernel.org \
    --cc=nhorman@redhat.com \
    --cc=pombredanne@nexb.com \
    --cc=sassmann@redhat.com \
    --cc=tglx@linutronix.de \
    /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.