linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Greg KH <greg@kroah.com>
Cc: linux-spdx@vger.kernel.org
Subject: Re: [patch 01/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_8.RULE
Date: Tue, 07 Jun 2022 14:14:32 +0200	[thread overview]
Message-ID: <87v8tc4qmv.ffs@tglx> (raw)
In-Reply-To: <Yp8vcm4WBF7mQi5p@kroah.com>

On Tue, Jun 07 2022 at 12:58, Greg KH wrote:
> On Mon, Jun 06, 2022 at 10:10:17PM +0200, Thomas Gleixner wrote:
>> ---
>>  Documentation/driver-api/vfio-mediated-device.rst |    4 +---
>>  arch/arm/boot/bootp/bootp.lds                     |    5 +----
>>  include/linux/input/elan-i2c-ids.h                |    5 +----
>>  3 files changed, 3 insertions(+), 11 deletions(-)
>
> I understand the goal to split this up per "rule", but that rule name
> makes no sense to any kernel developer.  They don't know what it is, or
> where it came from, or anything else like that.

I was just reusing the scripts/approach from 3 years ago :)

> This also touches files across subsystems, generally not a good idea.
> Is your goal to get acks from the people here and then split them up
> per-subsystem later, or are you thinking you want these merged as-is?

I assumed that we merge that through your spdx tree. Though it might be
not the worst idea to route them through the maintainers, so they become
more aware of the overall problem.

It's easy enough to split them fully automated after we got green light
from the folks on the SPDX list.

> Oh, and thanks for picking this work up again.  It's amazing to me that
> the companies/people that complain about this over the years never
> actually send patches to do anything about it...

What's more amazing is that we still have no plan what to do with the
more complicated ones - the non-standard disclaimers are just the tip of
the iceberg.

Thanks,

        tglx

  reply	other threads:[~2022-06-07 12:14 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 20:10 [patch repost 00/25] The first batch of various GPLv2 boilerplates and references Thomas Gleixner
2022-06-06 20:10 ` [patch 01/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_8.RULE Thomas Gleixner
2022-06-07  9:36   ` Allison Randal
2022-06-07 10:58   ` Greg KH
2022-06-07 12:14     ` Thomas Gleixner [this message]
2022-06-07 12:49       ` Greg KH
2022-06-06 20:10 ` [patch 02/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_13.RULE Thomas Gleixner
2022-06-06 20:10 ` [patch 05/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_133.RULE Thomas Gleixner
2022-06-07 11:38   ` Allison Randal
2022-06-06 20:10 ` [patch 06/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_147.RULE Thomas Gleixner
2022-06-07 11:39   ` Allison Randal
2022-06-06 20:10 ` [patch 07/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_149.RULE Thomas Gleixner
2022-06-07 11:41   ` Allison Randal
2022-06-06 20:10 ` [patch 08/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_152.RULE Thomas Gleixner
2022-06-07 11:42   ` Allison Randal
2022-06-06 20:10 ` [patch 09/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_160.RULE Thomas Gleixner
2022-06-07 11:43   ` Allison Randal
2022-06-06 20:10 ` [patch 11/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_179.RULE Thomas Gleixner
2022-06-07 11:44   ` Allison Randal
2022-06-06 20:10 ` [patch 12/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_208.RULE Thomas Gleixner
2022-06-06 20:10 ` [patch 13/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_240.RULE Thomas Gleixner
2022-06-06 20:10 ` [patch 14/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_292.RULE Thomas Gleixner
2022-06-07 11:50   ` Allison Randal
2022-06-06 20:10 ` [patch 15/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_298.RULE Thomas Gleixner
2022-06-07 11:51   ` Allison Randal
2022-06-06 20:10 ` [patch 16/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_318.RULE Thomas Gleixner
2022-06-07 11:52   ` Allison Randal
2022-06-06 20:10 ` [patch 17/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_319.RULE Thomas Gleixner
2022-06-07 11:54   ` Allison Randal
2022-06-06 20:10 ` [patch 18/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_320.RULE Thomas Gleixner
2022-06-07 11:57   ` Allison Randal
2022-06-06 20:10 ` [patch 19/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_347.RULE Thomas Gleixner
2022-06-06 20:14   ` Richard Fontana
2022-06-06 20:10 ` [patch 20/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_385.RULE Thomas Gleixner
2022-06-07 11:58   ` Allison Randal
2022-06-06 20:10 ` [patch 21/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_390.RULE Thomas Gleixner
2022-06-07 12:00   ` Allison Randal
2022-06-06 20:10 ` [patch 22/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_391.RULE Thomas Gleixner
2022-06-07 12:05   ` Allison Randal
2022-06-06 20:10 ` [patch 23/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_398.RULE Thomas Gleixner
2022-06-07 12:06   ` Allison Randal
2022-06-06 20:10 ` [patch 24/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_406.RULE Thomas Gleixner
2022-06-07 12:07   ` Allison Randal
2022-06-06 20:10 ` [patch 25/25] treewide: Replace GPLv2 boilerplate/reference with SPDX - gpl-2.0_409.RULE Thomas Gleixner
2022-06-07 10:34 ` [patch repost 00/25] The first batch of various GPLv2 boilerplates and references Thomas Gleixner

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=87v8tc4qmv.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=greg@kroah.com \
    --cc=linux-spdx@vger.kernel.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).