All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: "Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>
Cc: linux-next@vger.kernel.org, dri-devel@lists.freedesktop.org,
	amd-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: build failure of next-20220817 for amdgpu
Date: Wed, 17 Aug 2022 23:02:34 +0100	[thread overview]
Message-ID: <Yv1lepjhg/6QKyQl@debian> (raw)

Hi All,

Not sure if it has been reported, build of next-20220817 fails with the
error:

ERROR: modpost: "cpu_smallcore_map" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!

Trying to do a git bisect to find out the offending commit.

I will be happy to test any patch or provide any extra log if needed.


--
Regards
Sudip

WARNING: multiple messages have this Message-ID (diff)
From: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
To: "Alex Deucher" <alexander.deucher@amd.com>,
	"Christian König" <christian.koenig@amd.com>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: build failure of next-20220817 for amdgpu
Date: Wed, 17 Aug 2022 23:02:34 +0100	[thread overview]
Message-ID: <Yv1lepjhg/6QKyQl@debian> (raw)

Hi All,

Not sure if it has been reported, build of next-20220817 fails with the
error:

ERROR: modpost: "cpu_smallcore_map" [drivers/gpu/drm/amd/amdgpu/amdgpu.ko] undefined!

Trying to do a git bisect to find out the offending commit.

I will be happy to test any patch or provide any extra log if needed.


--
Regards
Sudip

             reply	other threads:[~2022-08-18  2:12 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-17 22:02 Sudip Mukherjee (Codethink) [this message]
2022-08-17 22:02 ` build failure of next-20220817 for amdgpu Sudip Mukherjee (Codethink)
2022-08-18  2:01 ` Alex Deucher
2022-08-18  2:01   ` Alex Deucher
2022-08-18  2:01   ` Alex Deucher
2022-08-18  2:09   ` Randy Dunlap
2022-08-18  2:09     ` Randy Dunlap
2022-08-18  2:09     ` Randy Dunlap
2022-08-18 10:43     ` Sudip Mukherjee
2022-08-18 10:43       ` Sudip Mukherjee
2022-08-18 10:43       ` Sudip Mukherjee
2022-08-18 15:10       ` Randy Dunlap
2022-08-18 15:10         ` Randy Dunlap
2022-08-18 15:10         ` Randy Dunlap
2022-08-18 19:15         ` build failure of next-20220817 for amdgpu due to 7bc913085765 ("drm/amdkfd: Try to schedule bottom half on same core") Sudip Mukherjee
2022-08-18 19:15           ` Sudip Mukherjee
2022-08-18 19:15           ` Sudip Mukherjee
2022-08-18 19:34           ` Randy Dunlap
2022-08-18 19:34             ` Randy Dunlap
2022-08-18 19:34             ` Randy Dunlap
2022-08-19 18:04             ` Felix Kuehling
2022-08-19 18:04               ` Felix Kuehling
2022-08-19 18:04               ` Felix Kuehling

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=Yv1lepjhg/6QKyQl@debian \
    --to=sudipm.mukherjee@gmail.com \
    --cc=Xinhui.Pan@amd.com \
    --cc=airlied@linux.ie \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=christian.koenig@amd.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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.