From: kernel test robot <lkp@intel.com>
To: Nipun Gupta <nipun.gupta@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC PATCH 1/2] drivers/misc: add silex multipk driver
Date: Thu, 13 Mar 2025 19:47:25 +0800 [thread overview]
Message-ID: <202503131951.mXFrHhEv-lkp@intel.com> (raw)
In-Reply-To: <20250312095421.1839220-1-nipun.gupta@amd.com>
Hi Nipun,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:
[auto build test ERROR on char-misc/char-misc-testing]
[also build test ERROR on char-misc/char-misc-next char-misc/char-misc-linus robh/for-next soc/for-next linus/master v6.14-rc6 next-20250313]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Nipun-Gupta/dt-bindings-add-device-tree-binding-for-silex-multipk/20250312-175851
base: char-misc/char-misc-testing
patch link: https://lore.kernel.org/r/20250312095421.1839220-1-nipun.gupta%40amd.com
patch subject: [RFC PATCH 1/2] drivers/misc: add silex multipk driver
config: x86_64-buildonly-randconfig-003-20250313 (https://download.01.org/0day-ci/archive/20250313/202503131951.mXFrHhEv-lkp@intel.com/config)
compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250313/202503131951.mXFrHhEv-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202503131951.mXFrHhEv-lkp@intel.com/
All errors (new ones prefixed by >>):
>> error: include/uapi/misc/silex_mpk.h: missing "WITH Linux-syscall-note" for SPDX-License-Identifier
make[3]: *** [scripts/Makefile.headersinst:63: usr/include/misc/silex_mpk.h] Error 1 shuffle=3739512866
make[3]: Target '__headers' not remade because of errors.
make[2]: *** [Makefile:1365: headers] Error 2 shuffle=3739512866
make[2]: Target 'prepare' not remade because of errors.
make[1]: *** [Makefile:251: __sub-make] Error 2 shuffle=3739512866
make[1]: Target 'prepare' not remade because of errors.
make: *** [Makefile:251: __sub-make] Error 2 shuffle=3739512866
make: Target 'prepare' not remade because of errors.
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-03-13 11:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 9:54 [RFC PATCH 1/2] drivers/misc: add silex multipk driver Nipun Gupta
2025-03-12 9:54 ` [RFC PATCH 2/2] dt-bindings: add device tree binding for silex multipk Nipun Gupta
2025-03-12 10:51 ` Krzysztof Kozlowski
2025-03-13 9:25 ` Gupta, Nipun
2025-03-13 9:38 ` Krzysztof Kozlowski
2025-03-13 9:43 ` Greg KH
2025-03-12 10:15 ` [RFC PATCH 1/2] drivers/misc: add silex multipk driver Greg KH
2025-03-12 10:18 ` Greg KH
2025-03-13 9:16 ` Gupta, Nipun
2025-03-13 9:41 ` Greg KH
2025-03-12 10:54 ` Krzysztof Kozlowski
2025-03-13 9:37 ` Gupta, Nipun
2025-03-13 11:47 ` kernel test robot [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=202503131951.mXFrHhEv-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nipun.gupta@amd.com \
--cc=oe-kbuild-all@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.