From: kernel test robot <lkp@intel.com>
To: Xiong Zhang <xiong.y.zhang@intel.com>, intel-gfx@lists.freedesktop.org
Cc: jani.nikula@intel.com, clang-built-linux@googlegroups.com,
kbuild-all@lists.01.org, chris@chris-wilson.co.uk
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Try to guess PCH type even without ISA bridge
Date: Mon, 14 Dec 2020 20:50:05 +0800 [thread overview]
Message-ID: <202012142054.4rnzVOVm-lkp@intel.com> (raw)
In-Reply-To: <20201214070113.16177-1-xiong.y.zhang@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2784 bytes --]
Hi Xiong,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip v5.10 next-20201211]
[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/Xiong-Zhang/drm-i915-Try-to-guess-PCH-type-even-without-ISA-bridge/20201214-150157
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-randconfig-a002-20201214 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project d38205144febf4dc42c9270c6aa3d978f1ef65e1)
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
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://github.com/0day-ci/linux/commit/718272991fa5c06a48629bce020ecfbdea006f96
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Xiong-Zhang/drm-i915-Try-to-guess-PCH-type-even-without-ISA-bridge/20201214-150157
git checkout 718272991fa5c06a48629bce020ecfbdea006f96
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/i915/intel_pch.c:187:6: warning: no previous prototype for function 'intel_detect_pch_virt' [-Wmissing-prototypes]
void intel_detect_pch_virt(struct drm_i915_private *dev_priv)
^
drivers/gpu/drm/i915/intel_pch.c:187:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void intel_detect_pch_virt(struct drm_i915_private *dev_priv)
^
static
1 warning generated.
vim +/intel_detect_pch_virt +187 drivers/gpu/drm/i915/intel_pch.c
186
> 187 void intel_detect_pch_virt(struct drm_i915_private *dev_priv)
188 {
189 unsigned short id;
190 enum intel_pch pch_type;
191
192 id = intel_virt_detect_pch(dev_priv);
193 pch_type = intel_pch_type(dev_priv, id);
194
195 /* Sanity check virtual PCH id */
196 if (drm_WARN_ON(&dev_priv->drm,
197 id && pch_type == PCH_NONE))
198 id = 0;
199
200 dev_priv->pch_type = pch_type;
201 dev_priv->pch_id = id;
202 }
203
---
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: 31448 bytes --]
[-- Attachment #3: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-12-14 12:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 7:01 [Intel-gfx] [PATCH] drm/i915: Try to guess PCH type even without ISA bridge Xiong Zhang
2020-12-14 7:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2020-12-14 7:19 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2020-12-18 9:05 ` [Intel-gfx] [PATCH v2] " Xiong Zhang
2020-12-22 5:15 ` Zhenyu Wang
2020-12-23 8:39 ` Zhang, Xiong Y
2020-12-23 8:59 ` Jani Nikula
2020-12-24 2:42 ` Zhang, Xiong Y
2020-12-24 2:54 ` Zhang, Xiong Y
2020-12-24 4:49 ` Zhenyu Wang
2021-01-13 4:53 ` [Intel-gfx] [PATCH v3] " Xiong Zhang
2021-01-14 0:58 ` [Intel-gfx] [PATCH v4] " Xiong Zhang
2021-01-14 5:14 ` Zhenyu Wang
2021-01-15 10:50 ` Jani Nikula
2021-01-15 11:01 ` Joonas Lahtinen
2021-01-18 6:04 ` Zhenyu Wang
2021-01-18 9:56 ` Jani Nikula
2020-12-18 10:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Try to guess PCH type even without ISA bridge (rev2) Patchwork
2020-12-18 11:27 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-01-13 5:23 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Try to guess PCH type even without ISA bridge (rev3) Patchwork
2021-01-13 5:52 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-01-14 2:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Try to guess PCH type even without ISA bridge (rev4) Patchwork
2021-01-14 4:59 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-12-14 7:22 ` [Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915: Try to guess PCH type even without ISA bridge Patchwork
2020-12-14 7:47 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-12-14 9:25 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-12-14 10:10 ` [Intel-gfx] [PATCH] " kernel test robot
2020-12-14 10:10 ` [Intel-gfx] [RFC PATCH] drm/i915: intel_detect_pch_virt() can be static kernel test robot
2020-12-14 12:50 ` 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=202012142054.4rnzVOVm-lkp@intel.com \
--to=lkp@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=clang-built-linux@googlegroups.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=xiong.y.zhang@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