All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Eric Sandeen <sandeen@redhat.com>,
	xfs <linux-xfs@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: WTF? Re: [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license
Date: Tue, 7 Nov 2017 09:20:42 -0800	[thread overview]
Message-ID: <20171107172042.GB26910@magnolia> (raw)
In-Reply-To: <20171107073940.GB4654@kroah.com>

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

  parent reply	other threads:[~2017-11-07 17:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-07  2:06 [PATCH] License cleanup: add SPDX GPL-2.0 license identifier to files with no license Darrick J. Wong
2017-11-07  7:20 ` WTF? " Christoph Hellwig
2017-11-07  7:39   ` Greg Kroah-Hartman
2017-11-07 17:07     ` Alan Cox
2017-11-07 17:12       ` Greg Kroah-Hartman
2017-11-07 17:25         ` Alan Cox
2017-11-07 18:30           ` Greg Kroah-Hartman
2017-11-07 17:20     ` Darrick J. Wong [this message]
2017-11-07 18:29       ` Greg Kroah-Hartman
2017-11-07 18:46         ` Alan Cox
2017-11-07 19:15           ` Theodore Ts'o
2017-11-07 19:28             ` Christoph Hellwig
2017-11-07 20:26               ` Greg Kroah-Hartman
2017-11-07 21:42                 ` Luis R. Rodriguez
2017-11-08  6:37                   ` Greg Kroah-Hartman
2017-11-08 17:19                   ` Alan Cox
2017-11-08 18:46                 ` Darrick J. Wong
2017-11-09  8:19                   ` Greg Kroah-Hartman
2017-11-08 12:35               ` Philippe Ombredanne
2017-11-08 15:11                 ` Christoph Hellwig
2017-11-08 18:06                   ` Christoph Hellwig
2017-11-09  8:23                   ` Greg Kroah-Hartman
2017-11-09  8:53                     ` Christoph Hellwig
2017-11-22 17:07                 ` Pavel Machek
2017-11-22 17:53                   ` Greg Kroah-Hartman
2017-11-25 19:12                     ` Pavel Machek
2017-11-25 21:57                       ` Joe Perches
2017-11-27 16:50                       ` Darrick J. Wong
2017-11-22 16:19             ` Pavel Machek
2017-11-08 23:47         ` Dave Chinner
2017-11-09  8:16           ` Greg Kroah-Hartman
2017-11-10 21:10             ` Alan Cox

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=20171107172042.GB26910@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@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.