From: kernel test robot <lkp@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [PATCH 03/10] drm/i915: move i915_buddy slab to direct module init/exit
Date: Sat, 24 Jul 2021 15:38:16 +0800 [thread overview]
Message-ID: <202107241531.7u4sxP5f-lkp@intel.com> (raw)
In-Reply-To: <20210723192934.1004427-3-daniel.vetter@ffwll.ch>
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next drm/drm-next v5.14-rc2 next-20210723]
[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/Daniel-Vetter/drm-i915-Check-for-nomodeset-in-i915_init-first/20210724-033145
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/8f4fee59edb0b93bec857359db320e589133e593
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Daniel-Vetter/drm-i915-Check-for-nomodeset-in-i915_init-first/20210724-033145
git checkout 8f4fee59edb0b93bec857359db320e589133e593
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/i915/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/i915_buddy.c:13:19: sparse: sparse: symbol 'slab_blocks' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
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: 42204 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
DRI Development <dri-devel@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [PATCH 03/10] drm/i915: move i915_buddy slab to direct module init/exit
Date: Sat, 24 Jul 2021 15:38:16 +0800 [thread overview]
Message-ID: <202107241531.7u4sxP5f-lkp@intel.com> (raw)
In-Reply-To: <20210723192934.1004427-3-daniel.vetter@ffwll.ch>
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next drm/drm-next v5.14-rc2 next-20210723]
[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/Daniel-Vetter/drm-i915-Check-for-nomodeset-in-i915_init-first/20210724-033145
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/8f4fee59edb0b93bec857359db320e589133e593
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Daniel-Vetter/drm-i915-Check-for-nomodeset-in-i915_init-first/20210724-033145
git checkout 8f4fee59edb0b93bec857359db320e589133e593
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/i915/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/i915_buddy.c:13:19: sparse: sparse: symbol 'slab_blocks' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
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: 42204 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
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [Intel-gfx] [PATCH 03/10] drm/i915: move i915_buddy slab to direct module init/exit
Date: Sat, 24 Jul 2021 15:38:16 +0800 [thread overview]
Message-ID: <202107241531.7u4sxP5f-lkp@intel.com> (raw)
In-Reply-To: <20210723192934.1004427-3-daniel.vetter@ffwll.ch>
[-- Attachment #1: Type: text/plain, Size: 1828 bytes --]
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-tip/drm-tip]
[cannot apply to drm-intel/for-linux-next drm-exynos/exynos-drm-next tegra-drm/drm/tegra/for-next drm/drm-next v5.14-rc2 next-20210723]
[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/Daniel-Vetter/drm-i915-Check-for-nomodeset-in-i915_init-first/20210724-033145
base: git://anongit.freedesktop.org/drm/drm-tip drm-tip
config: x86_64-rhel-8.3-kselftests (attached as .config)
compiler: gcc-10 (Ubuntu 10.3.0-1ubuntu1~20.04) 10.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-341-g8af24329-dirty
# https://github.com/0day-ci/linux/commit/8f4fee59edb0b93bec857359db320e589133e593
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Daniel-Vetter/drm-i915-Check-for-nomodeset-in-i915_init-first/20210724-033145
git checkout 8f4fee59edb0b93bec857359db320e589133e593
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/gpu/drm/i915/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
>> drivers/gpu/drm/i915/i915_buddy.c:13:19: sparse: sparse: symbol 'slab_blocks' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 42204 bytes --]
next prev parent reply other threads:[~2021-07-24 7:38 UTC|newest]
Thread overview: 102+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-23 19:29 [PATCH 01/10] drm/i915: Check for nomodeset in i915_init() first Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-23 19:29 ` [PATCH 02/10] drm/i915: move i915_active slab to direct module init/exit Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-26 15:24 ` Jason Ekstrand
2021-07-26 15:24 ` [Intel-gfx] " Jason Ekstrand
2021-07-23 19:29 ` [PATCH 03/10] drm/i915: move i915_buddy " Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-24 7:38 ` kernel test robot [this message]
2021-07-24 7:38 ` kernel test robot
2021-07-24 7:38 ` kernel test robot
2021-07-24 7:38 ` [RFC PATCH] drm/i915: slab_blocks can be static kernel test robot
2021-07-24 7:38 ` kernel test robot
2021-07-24 7:38 ` [Intel-gfx] " kernel test robot
2021-07-26 15:26 ` [PATCH 03/10] drm/i915: move i915_buddy slab to direct module init/exit Jason Ekstrand
2021-07-26 15:26 ` [Intel-gfx] " Jason Ekstrand
2021-07-23 19:29 ` [PATCH 04/10] drm/i915: move intel_context " Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-24 11:45 ` kernel test robot
2021-07-24 11:45 ` kernel test robot
2021-07-24 11:45 ` kernel test robot
2021-07-24 11:45 ` [RFC PATCH] drm/i915: slab_ce can be static kernel test robot
2021-07-24 11:45 ` kernel test robot
2021-07-24 11:45 ` [Intel-gfx] " kernel test robot
2021-07-26 8:35 ` [Intel-gfx] [PATCH 04/10] drm/i915: move intel_context slab to direct module init/exit Tvrtko Ursulin
2021-07-26 8:35 ` Tvrtko Ursulin
2021-07-26 15:30 ` Jason Ekstrand
2021-07-26 15:30 ` Jason Ekstrand
2021-07-26 15:42 ` Jason Ekstrand
2021-07-26 15:42 ` Jason Ekstrand
2021-07-26 16:08 ` Tvrtko Ursulin
2021-07-26 16:08 ` Tvrtko Ursulin
2021-07-26 16:20 ` Jason Ekstrand
2021-07-26 16:20 ` Jason Ekstrand
2021-07-26 16:31 ` Tvrtko Ursulin
2021-07-26 16:31 ` Tvrtko Ursulin
2021-07-26 18:17 ` Jason Ekstrand
2021-07-26 18:17 ` Jason Ekstrand
2021-07-27 10:14 ` Tvrtko Ursulin
2021-07-27 10:14 ` Tvrtko Ursulin
2021-07-23 19:29 ` [PATCH 05/10] drm/i915: move gem_context " Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-24 14:50 ` kernel test robot
2021-07-24 14:50 ` kernel test robot
2021-07-24 14:50 ` kernel test robot
2021-07-24 14:50 ` [RFC PATCH] drm/i915: slab_luts can be static kernel test robot
2021-07-24 14:50 ` kernel test robot
2021-07-24 14:50 ` [Intel-gfx] " kernel test robot
2021-07-26 15:35 ` [PATCH 05/10] drm/i915: move gem_context slab to direct module init/exit Jason Ekstrand
2021-07-26 15:35 ` [Intel-gfx] " Jason Ekstrand
2021-07-23 19:29 ` [PATCH 06/10] drm/i915: move gem_objects " Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-24 18:23 ` kernel test robot
2021-07-24 18:23 ` kernel test robot
2021-07-24 18:23 ` kernel test robot
2021-07-24 18:23 ` [RFC PATCH] drm/i915: slab_objects can be static kernel test robot
2021-07-24 18:23 ` kernel test robot
2021-07-24 18:23 ` [Intel-gfx] " kernel test robot
2021-07-26 15:39 ` [PATCH 06/10] drm/i915: move gem_objects slab to direct module init/exit Jason Ekstrand
2021-07-26 15:39 ` [Intel-gfx] " Jason Ekstrand
2021-07-23 19:29 ` [PATCH 07/10] drm/i915: move request slabs " Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-24 21:58 ` kernel test robot
2021-07-24 21:58 ` kernel test robot
2021-07-24 21:58 ` [Intel-gfx] " kernel test robot
2021-07-24 21:58 ` [RFC PATCH] drm/i915: slab_requests can be static kernel test robot
2021-07-24 21:58 ` kernel test robot
2021-07-24 21:58 ` [Intel-gfx] " kernel test robot
2021-07-26 15:46 ` [PATCH 07/10] drm/i915: move request slabs to direct module init/exit Jason Ekstrand
2021-07-26 15:46 ` [Intel-gfx] " Jason Ekstrand
2021-07-23 19:29 ` [PATCH 08/10] drm/i915: move scheduler " Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-25 1:23 ` kernel test robot
2021-07-25 1:23 ` kernel test robot
2021-07-25 1:23 ` kernel test robot
2021-07-25 1:23 ` [RFC PATCH] drm/i915: slab_dependencies can be static kernel test robot
2021-07-25 1:23 ` kernel test robot
2021-07-25 1:23 ` [Intel-gfx] " kernel test robot
2021-07-26 15:47 ` [PATCH 08/10] drm/i915: move scheduler slabs to direct module init/exit Jason Ekstrand
2021-07-26 15:47 ` [Intel-gfx] " Jason Ekstrand
2021-07-23 19:29 ` [PATCH 09/10] drm/i915: move vma slab " Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-25 4:04 ` kernel test robot
2021-07-25 4:04 ` kernel test robot
2021-07-25 4:04 ` [Intel-gfx] " kernel test robot
2021-07-25 4:04 ` [RFC PATCH] drm/i915: slab_vmas can be static kernel test robot
2021-07-25 4:04 ` kernel test robot
2021-07-25 4:04 ` [Intel-gfx] " kernel test robot
2021-07-26 15:50 ` [PATCH 09/10] drm/i915: move vma slab to direct module init/exit Jason Ekstrand
2021-07-26 15:50 ` [Intel-gfx] " Jason Ekstrand
2021-07-23 19:29 ` [PATCH 10/10] drm/i915: Remove i915_globals Daniel Vetter
2021-07-23 19:29 ` [Intel-gfx] " Daniel Vetter
2021-07-26 15:51 ` Jason Ekstrand
2021-07-26 15:51 ` [Intel-gfx] " Jason Ekstrand
2021-07-27 11:34 ` Daniel Vetter
2021-07-27 11:34 ` [Intel-gfx] " Daniel Vetter
2021-07-23 21:55 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [01/10] drm/i915: Check for nomodeset in i915_init() first Patchwork
2021-07-23 21:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-07-23 22:29 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-07-24 9:00 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2021-07-26 15:23 ` [PATCH 01/10] " Jason Ekstrand
2021-07-26 15:23 ` [Intel-gfx] " Jason Ekstrand
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=202107241531.7u4sxP5f-lkp@intel.com \
--to=lkp@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.