From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [android-common:android14-5.15 1/1] spdxcheck: include/uapi/linux/android_fuse.h: 1:57 Exception not valid for license BSD-3-CLAUSE: Linux-syscall-note
Date: Sat, 26 Nov 2022 05:19:02 +0800 [thread overview]
Message-ID: <202211260524.fwSWKTKK-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check warning: include/uapi/linux/android_fuse.h: 1:57 Exception not valid for license BSD-3-CLAUSE: Linux-syscall-note"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: cros-kernel-buildreports@googlegroups.com
tree: https://android.googlesource.com/kernel/common android14-5.15
head: 5853a069e0fdf286bc1904f187538bcee6d3c70d
commit: 9bc75534b343be508a9a492afc9699caa807da26 [1/1] ANDROID: fuse-bpf v1.1
:::::: branch date: 31 hours ago
:::::: commit date: 7 days ago
reproduce:
scripts/spdxcheck.py
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
spdxcheck warnings: (new ones prefixed by >>)
>> include/uapi/linux/android_fuse.h: 1:57 Exception not valid for license BSD-3-CLAUSE: Linux-syscall-note
tools/testing/selftests/rseq/compiler.h: 1:28 Invalid License ID: LGPL-2.1-only
tools/testing/selftests/rseq/rseq-generic-thread-pointer.h: 1:28 Invalid License ID: LGPL-2.1-only
tools/testing/selftests/rseq/rseq-ppc-thread-pointer.h: 1:28 Invalid License ID: LGPL-2.1-only
tools/testing/selftests/rseq/rseq-thread-pointer.h: 1:28 Invalid License ID: LGPL-2.1-only
tools/testing/selftests/rseq/rseq-x86-thread-pointer.h: 1:28 Invalid License ID: LGPL-2.1-only
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-11-25 21:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202211260524.fwSWKTKK-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild@lists.linux.dev \
/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.