From: kernel test robot <lkp@intel.com>
To: David Gow <davidgow@google.com>, Rae Moar <rmoar@google.com>,
Marie Zhussupova <marievic@google.com>,
marievictoria875@gmail.com, Rodrigo Vivi <rodrigo.vivi@intel.com>,
Shuah Khan <skhan@linuxfoundation.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
David Gow <davidgow@google.com>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
intel-xe@lists.freedesktop.org, kunit-dev@googlegroups.com,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/xe/tests: Fix some additional gen_params signatures
Date: Thu, 21 Aug 2025 02:31:13 +0800 [thread overview]
Message-ID: <202508210248.4CiPvWGD-lkp@intel.com> (raw)
In-Reply-To: <20250819073434.1411114-1-davidgow@google.com>
Hi David,
kernel test robot noticed the following build errors:
[auto build test ERROR on shuah-kselftest/kunit]
[also build test ERROR on linus/master v6.17-rc2 next-20250820]
[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/David-Gow/kunit-Only-output-a-test-plan-if-we-re-using-kunit_array_gen_params/20250819-154731
base: https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git kunit
patch link: https://lore.kernel.org/r/20250819073434.1411114-1-davidgow%40google.com
patch subject: [PATCH 1/2] drm/xe/tests: Fix some additional gen_params signatures
config: x86_64-randconfig-071-20250820 (https://download.01.org/0day-ci/archive/20250821/202508210248.4CiPvWGD-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250821/202508210248.4CiPvWGD-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/202508210248.4CiPvWGD-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from <built-in>:4:
>> drivers/gpu/drm/xe/tests/xe_pci_test.h:28:49: error: declaration of 'struct kunit' will not be visible outside of this function [-Werror,-Wvisibility]
28 | const void *xe_pci_graphics_ip_gen_param(struct kunit *test, const void *prev, char *desc);
| ^
drivers/gpu/drm/xe/tests/xe_pci_test.h:29:46: error: declaration of 'struct kunit' will not be visible outside of this function [-Werror,-Wvisibility]
29 | const void *xe_pci_media_ip_gen_param(struct kunit *test, const void *prev, char *desc);
| ^
drivers/gpu/drm/xe/tests/xe_pci_test.h:30:40: error: declaration of 'struct kunit' will not be visible outside of this function [-Werror,-Wvisibility]
30 | const void *xe_pci_id_gen_param(struct kunit *test, const void *prev, char *desc);
| ^
drivers/gpu/drm/xe/tests/xe_pci_test.h:31:49: error: declaration of 'struct kunit' will not be visible outside of this function [-Werror,-Wvisibility]
31 | const void *xe_pci_live_device_gen_param(struct kunit *test, const void *prev, char *desc);
| ^
4 errors generated.
vim +28 drivers/gpu/drm/xe/tests/xe_pci_test.h
27
> 28 const void *xe_pci_graphics_ip_gen_param(struct kunit *test, const void *prev, char *desc);
29 const void *xe_pci_media_ip_gen_param(struct kunit *test, const void *prev, char *desc);
30 const void *xe_pci_id_gen_param(struct kunit *test, const void *prev, char *desc);
31 const void *xe_pci_live_device_gen_param(struct kunit *test, const void *prev, char *desc);
32
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
parent reply other threads:[~2025-08-20 18:31 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20250819073434.1411114-1-davidgow@google.com>]
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=202508210248.4CiPvWGD-lkp@intel.com \
--to=lkp@intel.com \
--cc=davidgow@google.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=kunit-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=marievic@google.com \
--cc=marievictoria875@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rmoar@google.com \
--cc=rodrigo.vivi@intel.com \
--cc=skhan@linuxfoundation.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).