Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: ✗ Fi.CI.BUILD: failure for drm/i915: Create dumb buffer from LMEM
Date: Thu, 19 Sep 2019 20:49:26 -0000	[thread overview]
Message-ID: <20190919204926.23913.96603@emeril.freedesktop.org> (raw)
In-Reply-To: <20190919180433.12442-1-ramalingam.c@intel.com>

== Series Details ==

Series: drm/i915: Create dumb buffer from LMEM
URL   : https://patchwork.freedesktop.org/series/66950/
State : failure

== Summary ==

CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  DESCEND  objtool
  CHK     include/generated/compile.h
  AR      drivers/gpu/drm/i915/built-in.a
  CC [M]  drivers/gpu/drm/i915/i915_gem.o
drivers/gpu/drm/i915/i915_gem.c:162:23: error: ‘enum intel_region_id’ declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
   u32 *handle_p, enum intel_region_id mem_region)
                       ^~~~~~~~~~~~~~~
drivers/gpu/drm/i915/i915_gem.c:162:39: error: parameter 5 (‘mem_region’) has incomplete type
   u32 *handle_p, enum intel_region_id mem_region)
                                       ^~~~~~~~~~
drivers/gpu/drm/i915/i915_gem.c:159:1: error: function declaration isn’t a prototype [-Werror=strict-prototypes]
 i915_gem_create(struct drm_file *file,
 ^~~~~~~~~~~~~~~
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_create’:
drivers/gpu/drm/i915/i915_gem.c:174:20: error: ‘INTEL_MEMORY_LMEM’ undeclared (first use in this function); did you mean ‘INTEL_GEMINILAKE’?
  if (mem_region == INTEL_MEMORY_LMEM)
                    ^~~~~~~~~~~~~~~~~
                    INTEL_GEMINILAKE
drivers/gpu/drm/i915/i915_gem.c:174:20: note: each undeclared identifier is reported only once for each function it appears in
drivers/gpu/drm/i915/i915_gem.c:175:9: error: implicit declaration of function ‘i915_gem_object_create_lmem’; did you mean ‘i915_gem_object_create_shmem’? [-Werror=implicit-function-declaration]
   obj = i915_gem_object_create_lmem(dev_priv, size, 0);
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~
         i915_gem_object_create_shmem
drivers/gpu/drm/i915/i915_gem.c:175:7: error: assignment makes pointer from integer without a cast [-Werror=int-conversion]
   obj = i915_gem_object_create_lmem(dev_priv, size, 0);
       ^
drivers/gpu/drm/i915/i915_gem.c:176:25: error: ‘INTEL_MEMORY_STOLEN’ undeclared (first use in this function); did you mean ‘INTEL_MEMORY_LMEM’?
  else if (mem_region == INTEL_MEMORY_STOLEN)
                         ^~~~~~~~~~~~~~~~~~~
                         INTEL_MEMORY_LMEM
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_dumb_create’:
drivers/gpu/drm/i915/i915_gem.c:199:7: error: variable ‘mem_region’ has initializer but incomplete type
  enum intel_region_id mem_region = INTEL_MEMORY_UKNOWN;
       ^~~~~~~~~~~~~~~
drivers/gpu/drm/i915/i915_gem.c:199:36: error: ‘INTEL_MEMORY_UKNOWN’ undeclared (first use in this function); did you mean ‘INTEL_DRAM_UNKNOWN’?
  enum intel_region_id mem_region = INTEL_MEMORY_UKNOWN;
                                    ^~~~~~~~~~~~~~~~~~~
                                    INTEL_DRAM_UNKNOWN
drivers/gpu/drm/i915/i915_gem.c:199:23: error: storage size of ‘mem_region’ isn’t known
  enum intel_region_id mem_region = INTEL_MEMORY_UKNOWN;
                       ^~~~~~~~~~
drivers/gpu/drm/i915/i915_gem.c:227:6: error: implicit declaration of function ‘HAS_LMEM’; did you mean ‘HAS_GMCH’? [-Werror=implicit-function-declaration]
  if (HAS_LMEM(to_i915(dev)))
      ^~~~~~~~
      HAS_GMCH
drivers/gpu/drm/i915/i915_gem.c:228:16: error: ‘INTEL_MEMORY_LMEM’ undeclared (first use in this function); did you mean ‘INTEL_MEMORY_UKNOWN’?
   mem_region = INTEL_MEMORY_LMEM;
                ^~~~~~~~~~~~~~~~~
                INTEL_MEMORY_UKNOWN
drivers/gpu/drm/i915/i915_gem.c:199:23: error: unused variable ‘mem_region’ [-Werror=unused-variable]
  enum intel_region_id mem_region = INTEL_MEMORY_UKNOWN;
                       ^~~~~~~~~~
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_create_ioctl’:
drivers/gpu/drm/i915/i915_gem.c:250:39: error: ‘INTEL_MEMORY_UKNOWN’ undeclared (first use in this function); did you mean ‘INTEL_DRAM_UNKNOWN’?
           &args->size, &args->handle, INTEL_MEMORY_UKNOWN);
                                       ^~~~~~~~~~~~~~~~~~~
                                       INTEL_DRAM_UNKNOWN
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_dumb_create’:
drivers/gpu/drm/i915/i915_gem.c:232:1: error: control reaches end of non-void function [-Werror=return-type]
 }
 ^
drivers/gpu/drm/i915/i915_gem.c: In function ‘i915_gem_create_ioctl’:
drivers/gpu/drm/i915/i915_gem.c:251:1: error: control reaches end of non-void function [-Werror=return-type]
 }
 ^
cc1: all warnings being treated as errors
scripts/Makefile.build:280: recipe for target 'drivers/gpu/drm/i915/i915_gem.o' failed
make[4]: *** [drivers/gpu/drm/i915/i915_gem.o] Error 1
scripts/Makefile.build:497: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2
scripts/Makefile.build:497: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:497: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1083: recipe for target 'drivers' failed
make: *** [drivers] Error 2

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-09-19 20:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 18:04 [PATCH] drm/i915: Create dumb buffer from LMEM Ramalingam C
2019-09-19 20:05 ` Chris Wilson
2019-09-23 10:01   ` Ramalingam C
2019-09-19 20:49 ` Patchwork [this message]
2019-09-21 15:33 ` kbuild test robot
2019-09-21 15:42 ` kbuild test robot
2019-09-23  9:59 ` [PATCH v2] " Ramalingam C
2019-09-23 12:56 ` ✗ Fi.CI.BUILD: failure for drm/i915: Create dumb buffer from LMEM (rev2) Patchwork

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=20190919204926.23913.96603@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ramalingam.c@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