linux-kernel - Re: [PATCH v2 2/3] treewide: remove SPDX "WITH Linux-syscall-note" from kernel-space headers again

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 25 Jul 2019 10:40:34 +0200 (CEST)
From:   Thomas Gleixner <tglx@...utronix.de>
To:     Masahiro Yamada <yamada.masahiro@...ionext.com>
cc:     linux-kernel@...r.kernel.org, linux-spdx@...r.kernel.org,
        Greg KH <gregkh@...uxfoundation.org>,
        alsa-devel@...a-project.org
Subject: Re: [PATCH v2 2/3] treewide: remove SPDX "WITH Linux-syscall-note"
 from kernel-space headers again

On Thu, 25 Jul 2019, Masahiro Yamada wrote:

> The "WITH Linux-syscall-note" exception exists for headers exported to
> user space. It is strange to add it to non-exported headers.
> 
> Commit 687a3e4d8e61 ("treewide: remove SPDX "WITH Linux-syscall-note"
> from kernel-space headers") did cleanups some months ago, but it looks
> like we need to do this periodically.
> 
> This patch was generated by the following script:
> 
>   git grep -l -e Linux-syscall-note \
>     -- :*.h :^arch/*/include/uapi/asm/*.h :^include/uapi/ :^tools |
>   while read file
>   do
>           sed -i -e 's/(\(GPL-[^[:space:]]*\) WITH Linux-syscall-note)/\1/g' \
>           -e 's/ WITH Linux-syscall-note//g' $file
>   done
> 
> I did not commit drivers/staging/android/uapi/ion.h . This header is
> not currently exported, but somebody may plan to move it to include/uapi/
> when the time comes. I am not sure. Anyway, it will be better to check
> the license inconsistency in drivers/staging/android/uapi/.
> 
> Signed-off-by: Masahiro Yamada <yamada.masahiro@...ionext.com>

Reviewed-by: Thomas Gleixner <tglx@...utronix.de>