From: Joe Perches <joe@perches•com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel•com>,
Philippe Ombredanne <pombredanne@nexb•com>,
"Allan, Bruce W" <bruce.w.allan@intel•com>
Cc: "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>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Thomas Gleixner <tglx@linutronix•de>
Subject: Re: [net-next] intel: add SPDX identifiers to all the Intel drivers
Date: Tue, 20 Mar 2018 18:14:50 -0700 [thread overview]
Message-ID: <1521594890.12047.37.camel@perches.com> (raw)
In-Reply-To: <1521594560.15055.10.camel@intel.com>
On Tue, 2018-03-20 at 18:09 -0700, Jeff Kirsher wrote:
> On Tue, 2018-03-20 at 16:46 -0700, Philippe Ombredanne 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.
Why would exempting intel wired drivers be
necessary or useful?
I think it would be better if the kernel
source files used a consistent tag format.
The script I wrote is basically a sed that
simply updates the SPDX license text.
That is not particular different that Thomas's
original script that added the SPDX tags.
I have no intention of claiming anything like
a copyright on the output of a trivial script.
next prev parent reply other threads:[~2018-03-21 1:14 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 [this message]
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=1521594890.12047.37.camel@perches.com \
--to=joe@perches$(echo .)com \
--cc=bruce.w.allan@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=jogreene@redhat$(echo .)com \
--cc=kstewart@linuxfoundation$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=nhorman@redhat$(echo .)com \
--cc=pombredanne@nexb$(echo .)com \
--cc=sassmann@redhat$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
/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