From: kernel test robot <lkp@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org,
dri-devel@lists.freedesktop.org,
Jani Nikula <jani.nikula@linux.intel.com>,
Masahiro Yamada <masahiroy@kernel.org>,
Steven Price <steven.price@arm.com>,
Andrzej Hajda <a.hajda@samsung.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: remove IS_ACTIVE
Date: Sat, 2 Oct 2021 13:47:09 +0800 [thread overview]
Message-ID: <202110021346.qYSiODqI-lkp@intel.com> (raw)
In-Reply-To: <20211001074041.2076538-1-lucas.demarchi@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]
Hi Lucas,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next v5.15-rc3 next-20210823]
[cannot apply to airlied/drm-next]
[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]
url: https://github.com/0day-ci/linux/commits/Lucas-De-Marchi/drm-i915-remove-IS_ACTIVE/20211001-154226
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-r024-20211001 (attached as .config)
compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project 962e503cc8bc411f7523cc393acae8aae425b1c4)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/50006042f1d264599bd1be1942f9958112e15c01
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Lucas-De-Marchi/drm-i915-remove-IS_ACTIVE/20211001-154226
git checkout 50006042f1d264599bd1be1942f9958112e15c01
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/i915/i915_config.c:11:14: error: use of logical '&&' with constant operand [-Werror,-Wconstant-logical-operand]
if (context && CONFIG_DRM_I915_FENCE_TIMEOUT)
^ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/i915/i915_config.c:11:14: note: use '&' for a bitwise operation
if (context && CONFIG_DRM_I915_FENCE_TIMEOUT)
^~
&
drivers/gpu/drm/i915/i915_config.c:11:14: note: remove constant to silence this warning
if (context && CONFIG_DRM_I915_FENCE_TIMEOUT)
~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +11 drivers/gpu/drm/i915/i915_config.c
7
8 unsigned long
9 i915_fence_context_timeout(const struct drm_i915_private *i915, u64 context)
10 {
> 11 if (context && CONFIG_DRM_I915_FENCE_TIMEOUT)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 36679 bytes --]
prev parent reply other threads:[~2021-10-02 5:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-01 7:40 [Intel-gfx] [PATCH] drm/i915: remove IS_ACTIVE Lucas De Marchi
2021-10-01 7:46 ` Jani Nikula
2021-10-01 9:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
[not found] ` <163308055415.8412.14215483004176995847@build.alporthouse.com>
2021-10-01 9:57 ` [Intel-gfx] [PATCH] " Jani Nikula
2021-10-01 16:17 ` Lucas De Marchi
2021-10-04 20:52 ` Lucas De Marchi
2021-10-05 6:19 ` Dan Carpenter
2021-10-05 7:13 ` Lucas De Marchi
2021-10-01 10:51 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for " Patchwork
2021-10-01 12:48 ` [Intel-gfx] [PATCH] " kernel test robot
2021-10-01 22:07 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915: remove IS_ACTIVE (rev2) Patchwork
2021-10-02 5: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=202110021346.qYSiODqI-lkp@intel.com \
--to=lkp@intel.com \
--cc=a.hajda@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@lists.linux.dev \
--cc=lucas.demarchi@intel.com \
--cc=masahiroy@kernel.org \
--cc=steven.price@arm.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