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 v4 1/2] devcoredump: Add dev_coredumpm_timeout()
Date: Sun, 9 Jun 2024 09:35:22 +0800 [thread overview]
Message-ID: <202406090938.yRretx5x-lkp@intel.com> (raw)
In-Reply-To: <20240607193220.229760-1-jose.souza@intel.com>
Hi José,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on wireless/main linus/master v6.10-rc2 next-20240607]
[cannot apply to driver-core/driver-core-testing driver-core/driver-core-next driver-core/driver-core-linus wireless-next/main]
[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/20240608-033441
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20240607193220.229760-1-jose.souza%40intel.com
patch subject: [PATCH v4 1/2] devcoredump: Add dev_coredumpm_timeout()
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20240609/202406090938.yRretx5x-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240609/202406090938.yRretx5x-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/202406090938.yRretx5x-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from include/net/bluetooth/hci_core.h:36,
from net/bluetooth/coredump.c:10:
>> include/net/bluetooth/coredump.h:9: warning: "DEVCOREDUMP_TIMEOUT" redefined
9 | #define DEVCOREDUMP_TIMEOUT msecs_to_jiffies(10000) /* 10 sec */
|
In file included from net/bluetooth/coredump.c:6:
include/linux/devcoredump.h:16: note: this is the location of the previous definition
16 | #define DEVCOREDUMP_TIMEOUT (HZ * 60 * 5)
|
vim +/DEVCOREDUMP_TIMEOUT +9 include/net/bluetooth/coredump.h
9695ef876fd122 Abhishek Pandit-Subedi 2023-03-30 8
9695ef876fd122 Abhishek Pandit-Subedi 2023-03-30 @9 #define DEVCOREDUMP_TIMEOUT msecs_to_jiffies(10000) /* 10 sec */
9695ef876fd122 Abhishek Pandit-Subedi 2023-03-30 10
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-06-09 1:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 19:32 [PATCH v4 1/2] devcoredump: Add dev_coredumpm_timeout() José Roberto de Souza
2024-06-07 19:32 ` [PATCH v4 2/2] drm/xe: Increase devcoredump timeout José Roberto de Souza
2024-06-09 1:35 ` [PATCH v4 1/2] devcoredump: Add dev_coredumpm_timeout() kernel test robot
2024-06-09 1:35 ` kernel test robot [this message]
2024-06-09 4:53 ` kernel test robot
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=202406090938.yRretx5x-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