mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* [jbarnes:upstream-sync-points 2/2] drivers/gpu/drm/i915/i915_sync.c:43:12: sparse: symbol 'fence_lock' was not declared. Should it be static?
@ 2014-12-02 23:57 kbuild test robot
  2014-12-02 23:57 ` [PATCH jbarnes] drm/i915: fence_lock can be static kbuild test robot
  0 siblings, 1 reply; 2+ messages in thread
From: kbuild test robot @ 2014-12-02 23:57 UTC (permalink / raw)
  To: Jesse Barnes
  Cc: kbuild-all, Daniel Vetter, Jani Nikula, David Airlie, intel-gfx,
	dri-devel, linux-kernel

tree:   git://people.freedesktop.org/~jbarnes/linux upstream-sync-points
head:   97b242f63adaf11c3edf16b0282243cc4274eac8
commit: 97b242f63adaf11c3edf16b0282243cc4274eac8 [2/2] drm/i915: Android sync points for i915 v3
reproduce:
  # apt-get install sparse
  git checkout 97b242f63adaf11c3edf16b0282243cc4274eac8
  make ARCH=x86_64 allmodconfig
  make C=1 CF=-D__CHECK_ENDIAN__


sparse warnings: (new ones prefixed by >>)

>> drivers/gpu/drm/i915/i915_sync.c:43:12: sparse: symbol 'fence_lock' was not declared. Should it be static?

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
http://lists.01.org/mailman/listinfo/kbuild                 Intel Corporation

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-12-02 23:57 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-02 23:57 [jbarnes:upstream-sync-points 2/2] drivers/gpu/drm/i915/i915_sync.c:43:12: sparse: symbol 'fence_lock' was not declared. Should it be static? kbuild test robot
2014-12-02 23:57 ` [PATCH jbarnes] drm/i915: fence_lock can be static kbuild test robot

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®