dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	Karol Herbst <kherbst@redhat.com>,
	kbuild-all@01.org, dri-devel@lists.freedesktop.org
Subject: [radeon-alex:drm-next-5.2-wip 64/66] drivers/gpu/drm/ttm/ttm_bo.c:52:10: sparse: symbol 'ttm_bo_glob_use_count' was not declared. Should it be static?
Date: Sat, 20 Apr 2019 04:02:08 +0800	[thread overview]
Message-ID: <201904200447.V8Lm4m18%lkp@intel.com> (raw)

tree:   git://people.freedesktop.org/~agd5f/linux.git drm-next-5.2-wip
head:   a70be09f90c0b211b45bae50eb98617d75713297
commit: 5c4923919f015e80e76d3d88d5743d422d105ff2 [64/66] drm/ttm: fix re-init of global structures
reproduce:
        # apt-get install sparse
        git checkout 5c4923919f015e80e76d3d88d5743d422d105ff2
        make ARCH=x86_64 allmodconfig
        make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>



sparse warnings: (new ones prefixed by >>)

   drivers/gpu/drm/ttm/ttm_bo.c:51:1: sparse: symbol 'ttm_global_mutex' was not declared. Should it be static?
>> drivers/gpu/drm/ttm/ttm_bo.c:52:10: sparse: symbol 'ttm_bo_glob_use_count' was not declared. Should it be static?
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   drivers/gpu/drm/ttm/ttm_bo.c:559:28: sparse: context imbalance in 'ttm_bo_cleanup_refs' - unexpected unlock
   drivers/gpu/drm/ttm/ttm_bo.c:619:27: sparse: context imbalance in 'ttm_bo_delayed_delete' - different lock contexts for basic block
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   drivers/gpu/drm/ttm/ttm_bo.c:787:12: sparse: context imbalance in 'ttm_mem_evict_first' - different lock contexts for basic block
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression
   drivers/gpu/drm/ttm/ttm_bo.c:1765:5: sparse: context imbalance in 'ttm_bo_swapout' - different lock contexts for basic block
   include/linux/reservation.h:220:20: sparse: dereference of noderef expression
   include/linux/reservation.h:220:45: sparse: dereference of noderef expression

Please review and possibly fold the followup patch.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-04-19 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 20:02 kbuild test robot [this message]
2019-04-19 20:02 ` [RFC PATCH radeon-alex] drm/ttm: ttm_bo_glob_use_count can be static kbuild 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=201904200447.V8Lm4m18%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alexander.deucher@amd.com \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@01.org \
    --cc=kherbst@redhat.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