AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Christian König" <christian.koenig@amd.com>
Cc: Mauro Carvalho Chehab <mauro.chehab@linux.intel.com>,
	Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>,
	amd-gfx list <amd-gfx@lists.freedesktop.org>,
	"Deucher, Alexander" <alexander.deucher@amd.com>,
	Maling list - DRI developers <dri-devel@lists.freedesktop.org>,
	Alex Deucher <alexdeucher@gmail.com>
Subject: Re: [PATCH] Revert "drm/amdgpu: add drm buddy support to amdgpu"
Date: Mon, 18 Jul 2022 13:40:34 -0700	[thread overview]
Message-ID: <87zgh6b1dp.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <076231a3-38e9-e013-e106-aa926d009e77@amd.com>

On Thu, 14 Jul 2022 08:00:32 -0700, Christian König wrote:
>
> Am 14.07.22 um 15:33 schrieb Alex Deucher:
> > On Thu, Jul 14, 2022 at 9:09 AM Christian König
> > <christian.koenig@amd.com> wrote:
> >> Hi Mauro,
> >>
> >> well the last time I checked drm-tip was clean.
> >>
> >> The revert is necessary because we had some problems with the commit
> >> which we couldn't fix in the 5.19 cycle.
> > Would it be worth reverting the revert and applying the actual fix[1]?
> >   It's a huge revert unfortunately while the actual fix is like 10
> > lines of code.  I'm concerned there will be subtle fallout from the
> > revert due to how extensive it is.
>
> We have other bug fixes and cleanups around that patch which didn't made it
> into 5.19 either. I don't want to create an ever greater mess.
>
> Real question is why building drm-tip work for me but not for others?

Seeing this on latest drm-tip:

drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c:54:1: error: redefinition of ‘amdgpu_vram_mgr_first_block’
   54 | amdgpu_vram_mgr_first_block(struct list_head *list)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h:29,
                 from drivers/gpu/drm/amd/amdgpu/amdgpu.h:73,
                 from drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c:28:
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.h:57:1: note: previous definition of ‘amdgpu_vram_mgr_first_block’ with type ‘struct drm_buddy_block *(struct list_head *)’
   57 | amdgpu_vram_mgr_first_block(struct list_head *list)
      | ^~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c:59:20: error: redefinition of ‘amdgpu_is_vram_mgr_blocks_contiguous’
   59 | static inline bool amdgpu_is_vram_mgr_blocks_contiguous(struct list_head *head)
      |                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.h:62:20: note: previous definition of ‘amdgpu_is_vram_mgr_blocks_contiguous’ with type ‘bool(struct list_head *)’ {aka ‘_Bool(struct list_head *)’}
   62 | static inline bool amdgpu_is_vram_mgr_blocks_contiguous(struct list_head *head)
      |                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
make[4]: *** [scripts/Makefile.build:249: drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [scripts/Makefile.build:466: drivers/gpu/drm/amd/amdgpu] Error 2
make[2]: *** [scripts/Makefile.build:466: drivers/gpu/drm] Error 2
make[1]: *** [scripts/Makefile.build:466: drivers/gpu] Error 2

  reply	other threads:[~2022-07-18 20:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 10:21 [PATCH] Revert "drm/amdgpu: add drm buddy support to amdgpu" Arunpravin Paneer Selvam
2022-07-14  8:46 ` Thomas Zimmermann
2022-07-14 12:54 ` Mauro Carvalho Chehab
2022-07-14 13:08   ` Christian König
2022-07-14 13:19     ` Mauro Carvalho Chehab
2022-07-14 13:31       ` Christian König
2022-07-14 13:33     ` Alex Deucher
2022-07-14 14:34       ` Mauro Carvalho Chehab
2022-07-14 15:00       ` Christian König
2022-07-18 20:40         ` Dixit, Ashutosh [this message]
2022-08-04 15:52           ` Mike Lothian
2022-08-04 21:51             ` Dave Airlie

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=87zgh6b1dp.wl-ashutosh.dixit@intel.com \
    --to=ashutosh.dixit@intel.com \
    --cc=Arunpravin.PaneerSelvam@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=alexdeucher@gmail.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=mauro.chehab@linux.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