From: kernel test robot <lkp@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>,
linux-kernel@vger.kernel.org, intel-xe@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Mukesh Ojha" <quic_mojha@quicinc.com>,
"Johannes Berg" <johannes@sipsolutions.net>,
"Jonathan Cavitt" <jonathan.cavitt@intel.com>,
"José Roberto de Souza" <jose.souza@intel.com>
Subject: Re: [PATCH v5 1/2] devcoredump: Add dev_coredumpm_timeout()
Date: Tue, 11 Jun 2024 18:37:49 +0800 [thread overview]
Message-ID: <202406111852.SdIM9NWt-lkp@intel.com> (raw)
In-Reply-To: <20240610161133.156566-1-jose.souza@intel.com>
Hi José,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-xe/drm-xe-next]
[also build test ERROR on wireless-next/main wireless/main linus/master v6.10-rc3 next-20240611]
[cannot apply to driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus]
[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/Jos-Roberto-de-Souza/drm-xe-Increase-devcoredump-timeout/20240611-001400
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20240610161133.156566-1-jose.souza%40intel.com
patch subject: [PATCH v5 1/2] devcoredump: Add dev_coredumpm_timeout()
config: i386-randconfig-141-20240611 (https://download.01.org/0day-ci/archive/20240611/202406111852.SdIM9NWt-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240611/202406111852.SdIM9NWt-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/202406111852.SdIM9NWt-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from drivers/gpu/drm/xe/xe_devcoredump.c:9:
>> include/linux/devcoredump.h:79:6: error: no previous prototype for function 'dev_coredumpm_timeout' [-Werror,-Wmissing-prototypes]
79 | void dev_coredumpm_timeout(struct device *dev, struct module *owner,
| ^
include/linux/devcoredump.h:79:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
79 | void dev_coredumpm_timeout(struct device *dev, struct module *owner,
| ^
| static
1 error generated.
vim +/dev_coredumpm_timeout +79 include/linux/devcoredump.h
78
> 79 void dev_coredumpm_timeout(struct device *dev, struct module *owner,
80 void *data, size_t datalen, gfp_t gfp,
81 ssize_t (*read)(char *buffer, loff_t offset,
82 size_t count, void *data,
83 size_t datalen),
84 void (*free)(void *data),
85 unsigned long timeout)
86 {
87 free(data);
88 }
89
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-06-11 10:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 16:11 [PATCH v5 1/2] devcoredump: Add dev_coredumpm_timeout() José Roberto de Souza
2024-06-10 16:11 ` [PATCH v5 2/2] drm/xe: Increase devcoredump timeout José Roberto de Souza
2024-06-10 20:17 ` Rodrigo Vivi
2024-06-10 20:16 ` [PATCH v5 1/2] devcoredump: Add dev_coredumpm_timeout() Rodrigo Vivi
2024-06-10 20:42 ` Cavitt, Jonathan
2024-06-10 20:52 ` Souza, Jose
2024-06-10 22:00 ` Rodrigo Vivi
2024-06-11 6:19 ` kernel test robot
2024-06-11 10:37 ` 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=202406111852.SdIM9NWt-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=johannes@sipsolutions.net \
--cc=jonathan.cavitt@intel.com \
--cc=jose.souza@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=quic_mojha@quicinc.com \
--cc=rodrigo.vivi@intel.com \
/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