All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Arunpravin Paneer Selvam" <arunpravin.paneerselvam@amd.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/amdgpu: add drm buddy support to amdgpu (rev3)
Date: Thu, 07 Apr 2022 06:22:59 -0000	[thread overview]
Message-ID: <164931257907.14671.1075937881801061656@emeril.freedesktop.org> (raw)
In-Reply-To: <20220407054651.3924-1-Arunpravin.PaneerSelvam@amd.com>

== Series Details ==

Series: drm/amdgpu: add drm buddy support to amdgpu (rev3)
URL   : https://patchwork.freedesktop.org/series/100908/
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_drv.o
In file included from drivers/gpu/drm/amd/amdgpu/amdgpu.h:73,
                 from drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c:43:
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h:29:10: fatal error: amdgpu_vram_mgr.h: No such file or directory
 #include "amdgpu_vram_mgr.h"
          ^~~~~~~~~~~~~~~~~~~
compilation terminated.
scripts/Makefile.build:288: recipe for target 'drivers/gpu/drm/amd/amdgpu/amdgpu_drv.o' failed
make[4]: *** [drivers/gpu/drm/amd/amdgpu/amdgpu_drv.o] Error 1
scripts/Makefile.build:550: recipe for target 'drivers/gpu/drm/amd/amdgpu' failed
make[3]: *** [drivers/gpu/drm/amd/amdgpu] Error 2
scripts/Makefile.build:550: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2
scripts/Makefile.build:550: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1834: recipe for target 'drivers' failed
make: *** [drivers] Error 2



  parent reply	other threads:[~2022-04-07  6:23 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-07  5:46 [PATCH v12] drm/amdgpu: add drm buddy support to amdgpu Arunpravin Paneer Selvam
2022-04-07  5:46 ` Arunpravin Paneer Selvam
2022-04-07  5:46 ` [Intel-gfx] " Arunpravin Paneer Selvam
2022-04-07  6:10 ` Christian König
2022-04-07  6:10   ` Christian König
2022-04-07  6:10   ` [Intel-gfx] " Christian König
2022-04-07  6:22 ` Patchwork [this message]
2022-04-07 13:47 ` Paul Menzel
2022-04-07 13:47   ` Paul Menzel
2022-04-07 13:47   ` [Intel-gfx] " Paul Menzel
2022-04-26 15:29 ` Mike Lothian
2022-04-26 15:29   ` [Intel-gfx] " Mike Lothian
2022-04-26 16:36   ` Christian König
2022-04-26 16:36     ` [Intel-gfx] " Christian König
2022-04-27  5:26     ` Paneer Selvam, Arunpravin
2022-04-27  5:26       ` [Intel-gfx] " Paneer Selvam, Arunpravin
2022-04-27 11:55     ` Mike Lothian
2022-04-27 11:55       ` [Intel-gfx] " Mike Lothian
2022-05-02 15:11       ` Mike Lothian
2022-05-02 15:11         ` [Intel-gfx] " Mike Lothian
2022-05-02 15:54         ` Arunpravin Paneer Selvam
2022-05-02 15:54           ` [Intel-gfx] " Arunpravin Paneer Selvam
2022-05-02 16:31           ` Mike Lothian
2022-05-02 16:31             ` [Intel-gfx] " Mike Lothian
2022-05-16 12:40             ` Mike Lothian
2022-05-16 12:40               ` [Intel-gfx] " Mike Lothian
2022-05-16 15:05               ` Alex Deucher
2022-05-16 15:05                 ` [Intel-gfx] " Alex Deucher
2022-05-28  7:43                 ` Paneer Selvam, Arunpravin
2022-05-28  7:43                   ` [Intel-gfx] " Paneer Selvam, Arunpravin
2022-05-28 23:52                   ` Mike Lothian
2022-05-28 23:52                     ` Mike Lothian
2022-05-28 23:52                     ` [Intel-gfx] " Mike Lothian
2022-05-30  6:02                     ` Christian König
2022-05-30  6:02                       ` Christian König
2022-06-23 11:15                     ` Mike Lothian
2022-06-23 11:15                       ` Mike Lothian
2022-06-23 11:15                       ` [Intel-gfx] " Mike Lothian

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=164931257907.14671.1075937881801061656@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=arunpravin.paneerselvam@amd.com \
    --cc=intel-gfx@lists.freedesktop.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.