All of lore.kernel.org
 help / color / mirror / Atom feed
* Re: [PATCH] x86/mm: Add SPDX identifier in arch/x86/mm files
       [not found] <1548858044-4695-1-git-send-email-liu.xiang6@zte.com.cn>
@ 2019-01-30 18:05 ` Thomas Gleixner
  0 siblings, 0 replies; only message in thread
From: Thomas Gleixner @ 2019-01-30 18:05 UTC (permalink / raw)
  To: Liu Xiang
  Cc: x86, linux-kernel, dave.hansen, luto, peterz, mingo, bp, hpa,
	liuxiang_1999

[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]

On Wed, 30 Jan 2019, Liu Xiang wrote:
> --- a/arch/x86/mm/iomap_32.c
> +++ b/arch/x86/mm/iomap_32.c
> @@ -1,19 +1,7 @@
> +// SPDX-License-Identifier: GPL-2.0

This is wrong.

>  /*
>   * Copyright © 2008 Ingo Molnar
>   *
> - * This program is free software; you can redistribute it and/or modify
> - * it under the terms of the GNU General Public License as published by
> - * the Free Software Foundation; either version 2 of the License, or
> - * (at your option) any later version.

      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

And there are more of those wrongs.

Aside of that, you really need to differentiate between files, which do not
have any license notice or reference at all and those which have. For the
ones without adding the identifier is fine. For thos which have, you really
need to create separate patches and cc the copyright holder(s) and the
initial author if possible.

Just slapping random identifiers into source files is not helping anything,
actually it's making the problem worse because you are relicensing the
source files.

Thanks,

	tglx

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2019-01-30 18:05 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <1548858044-4695-1-git-send-email-liu.xiang6@zte.com.cn>
2019-01-30 18:05 ` [PATCH] x86/mm: Add SPDX identifier in arch/x86/mm files Thomas Gleixner

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.