linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Ombredanne <pombredanne@nexb.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Dave Airlie <airlied@gmail.com>,
	Alex Deucher <alexander.deucher@amd.com>,
	LKML <linux-kernel@vger.kernel.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [git pull] drm fixes for v4.15-rc3
Date: Sat, 9 Dec 2017 00:34:53 +0100	[thread overview]
Message-ID: <CAOFm3uGCqQFbEqEqYVMFjWXXm-UhoVo35ytUO5ebwEF9WOZekg@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFyBSiDAHpEzou2h=RSna1a2Fyi4hrJDME9D3m942VfU9A@mail.gmail.com>

Linus,

On Fri, Dec 8, 2017 at 10:16 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Thu, Dec 7, 2017 at 5:20 PM, Dave Airlie <airlied@gmail.com> wrote:
>>
>> This pull is a bit larger than I'd like but a large bunch of it is
>> license fixes, AMD wanted to fix the licenses for a bunch of files
>> that were missing them,
>
> Oh Christ, couldn't they have just added the one-liner SPDX tags
> rather than doing that crazy "new 22 line boiler plate garbage to
> fifteen random Makefiles"?
>
> I pulled it, but let's try to reign in the crazy "lets add filler
> lines" behavior, ok?
>
> Alex, can you talk to the AMD lawyers and ask them about just putting
> the SPDX line instead?
>
>                 Linus

You made my day! I shall add that every time someone sends a patch
with long legalese boilerplate instead of a shorter SDPX tag, there is
a kitten that dies somewhere.
-- 
Cordially
Philippe Ombredanne, your friendly kernel licensing decraper

      reply	other threads:[~2017-12-08 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-08  1:20 [git pull] drm fixes for v4.15-rc3 Dave Airlie
2017-12-08 21:16 ` Linus Torvalds
2017-12-08 23:34   ` Philippe Ombredanne [this message]

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=CAOFm3uGCqQFbEqEqYVMFjWXXm-UhoVo35ytUO5ebwEF9WOZekg@mail.gmail.com \
    --to=pombredanne@nexb.com \
    --cc=airlied@gmail.com \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).