All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Jim Cromie" <jim.cromie@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm: use dyndbg in drm_print (rev2)
Date: Fri, 16 Jul 2021 14:33:46 -0000	[thread overview]
Message-ID: <162644602669.12779.12485733563066272549@emeril.freedesktop.org> (raw)
In-Reply-To: <20210714175138.319514-1-jim.cromie@gmail.com>

== Series Details ==

Series: drm: use dyndbg in drm_print (rev2)
URL   : https://patchwork.freedesktop.org/series/92542/
State : failure

== Summary ==

CALL    scripts/checksyscalls.sh
  CALL    scripts/atomic/check-atomics.sh
  DESCEND objtool
  CHK     include/generated/compile.h
  CC [M]  drivers/gpu/drm/amd/amdgpu/amdgpu_fence.o
In file included from drivers/gpu/drm/amd/amdgpu/amdgpu_ring.h:29,
                 from drivers/gpu/drm/amd/amdgpu/amdgpu_ctx.h:26,
                 from drivers/gpu/drm/amd/amdgpu/amdgpu.h:43,
                 from drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:40:
drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c: In function ‘amdgpu_fence_driver_start_ring’:
./include/drm/drm_print.h:330:30: error: ‘struct device’ has no member named ‘dev’; did you mean ‘devt’?
  _drm_dev_dbg((drm) ? (drm)->dev : NULL, cls, fmt, ##__VA_ARGS__)
                              ^~~
./include/drm/drm_print.h:431:2: note: in expansion of macro ‘drm_dev_dbg’
  drm_dev_dbg(dev, cDRM_UT_CORE, fmt, ##__VA_ARGS__)
  ^~~~~~~~~~~
drivers/gpu/drm/amd/amdgpu/amdgpu_fence.c:427:2: note: in expansion of macro ‘DRM_DEV_DEBUG’
  DRM_DEV_DEBUG(adev->dev, "fence driver on ring %s use gpu addr 0x%016llx\n",
  ^~~~~~~~~~~~~
scripts/Makefile.build:271: recipe for target 'drivers/gpu/drm/amd/amdgpu/amdgpu_fence.o' failed
make[4]: *** [drivers/gpu/drm/amd/amdgpu/amdgpu_fence.o] Error 1
scripts/Makefile.build:514: recipe for target 'drivers/gpu/drm/amd/amdgpu' failed
make[3]: *** [drivers/gpu/drm/amd/amdgpu] Error 2
scripts/Makefile.build:514: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:514: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1841: 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:[~2021-07-16 14:33 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 17:51 [PATCH v3 0/5] drm: use dyndbg in drm_print Jim Cromie
2021-07-14 17:51 ` [Intel-gfx] " Jim Cromie
2021-07-14 17:51 ` Jim Cromie
2021-07-14 17:51 ` [PATCH v3 1/5] drm/print: fixup spelling in a comment Jim Cromie
2021-07-14 17:51   ` [Intel-gfx] " Jim Cromie
2021-07-14 17:51   ` Jim Cromie
2021-07-20 13:08   ` Daniel Vetter
2021-07-20 13:08     ` [Intel-gfx] " Daniel Vetter
2021-07-20 13:08     ` Daniel Vetter
2021-07-14 17:51 ` [PATCH v3 2/5] drm_print.h: rewrap __DRM_DEFINE_DBG_RATELIMITED macro Jim Cromie
2021-07-14 17:51   ` [Intel-gfx] " Jim Cromie
2021-07-14 17:51   ` Jim Cromie
2021-07-14 17:51 ` [PATCH v3 3/5] drm/print: RFC add choice to use dynamic debug in drm-debug Jim Cromie
2021-07-14 17:51   ` [Intel-gfx] " Jim Cromie
2021-07-14 17:51   ` Jim Cromie
2021-07-20 13:29   ` Daniel Vetter
2021-07-20 13:29     ` [Intel-gfx] " Daniel Vetter
2021-07-20 13:29     ` Daniel Vetter
2021-07-22 15:20     ` [Intel-gfx] " Sean Paul
2021-07-22 15:20       ` Sean Paul
2021-07-27 14:02       ` Sean Paul
2021-07-27 14:02         ` Sean Paul
2021-07-27 14:02         ` Sean Paul
2021-07-28 21:22         ` jim.cromie
2021-07-28 21:22           ` jim.cromie
2021-07-28 21:22           ` jim.cromie
2021-07-22 19:38     ` jim.cromie
2021-07-22 19:38       ` [Intel-gfx] " jim.cromie
2021-07-22 19:38       ` jim.cromie
2022-03-05 16:06     ` Jim Cromie
2022-03-05 16:06       ` [Intel-gfx] " Jim Cromie
2022-03-05 16:06       ` Jim Cromie
2021-07-14 17:51 ` [PATCH v3 4/5] drm/print: move conditional deref into macro defn Jim Cromie
2021-07-14 17:51   ` [Intel-gfx] " Jim Cromie
2021-07-14 17:51   ` Jim Cromie
2021-07-14 21:49   ` [Intel-gfx] " kernel test robot
2021-07-14 23:51     ` jim.cromie
2021-07-14 22:00   ` kernel test robot
2021-07-14 23:34   ` kernel test robot
2021-07-14 17:51 ` [PATCH v3 5/5] i915: map gvt pr_debug categories to bits in parameters/debug_gvt Jim Cromie
2021-07-14 17:51   ` [Intel-gfx] " Jim Cromie
2021-07-14 17:51   ` Jim Cromie
2021-07-16 14:33 ` Patchwork [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=162644602669.12779.12485733563066272549@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jim.cromie@gmail.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 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.