From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from aserp1040.oracle.com ([141.146.126.69]:32291 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752145AbdKGRVS (ORCPT ); Tue, 7 Nov 2017 12:21:18 -0500 Date: Tue, 7 Nov 2017 09:20:42 -0800 From: "Darrick J. Wong" Subject: Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license Message-ID: <20171107172042.GB26910@magnolia> References: <20171107020607.GA26910@magnolia> <20171107072040.GB4586@infradead.org> <20171107073940.GB4654@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171107073940.GB4654@kroah.com> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Greg Kroah-Hartman Cc: Christoph Hellwig , Eric Sandeen , xfs , linux-kernel@vger.kernel.org On Tue, Nov 07, 2017 at 08:39:40AM +0100, Greg Kroah-Hartman wrote: > On Mon, Nov 06, 2017 at 11:20:40PM -0800, Christoph Hellwig wrote: > > NAK, for both the libxfs patch and the kernel one. > > What libxfs patch? And what "kernel one" are you referring to here? > > > I wrote the file and it has no copyright header because it conatians > > trivial, non-copyrightable code. > > What file exactly? > > And from what I know, there is nothing that is "non-copyrightable". > > And this isn't changing the copyright of _ANYTHING_ it is just putting > the explicit license of the file, on each file in the kernel, because it > needs to be tracked. > > > I don't know why people think they can touch license information on > > files I've written without even asking me. > > Nothing was changed, the license should be the exact same as it was > before. But as I don't know what file you are referring to here, it's a > bit hard to determine what you are talking about exactly :( fs/xfs/libxfs/xfs_cksum.h --D > > thanks, > > greg k-h > -- > To unsubscribe from this list: send the line "unsubscribe linux-xfs" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html