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>,
	Hamza Mahfooz <hamza.mahfooz@amd.com>,
	Fangzhi Zuo <Jerry.Zuo@amd.com>
Cc: "David Airlie" <airlied@linux.ie>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-next@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	"Daniel Vetter" <daniel@ffwll.ch>,
	"Christian König" <christian.koenig@amd.com>
Subject: build failure of next-20220811 due to b1a63a0b48ad ("drm/amd/display: consider DSC pass-through during mode validation")
Date: Thu, 11 Aug 2022 18:10:48 +0100	[thread overview]
Message-ID: <YvU4GD8HtZ1A4dhI@debian> (raw)

Hi All,

Not sure if it has been reported, builds of riscv, alpha, s390, arm,
arm64, xtensa, mips, csky allmodconfig have failed to build next-20220811
with the error:

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

git bisect pointed to b1a63a0b48ad ("drm/amd/display: consider DSC pass-through during mode validation")
And, reverting that commit has fixed the build failure.

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>,
	Hamza Mahfooz <hamza.mahfooz@amd.com>,
	Fangzhi Zuo <Jerry.Zuo@amd.com>
Cc: "Christian König" <christian.koenig@amd.com>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	"David Airlie" <airlied@linux.ie>,
	"Daniel Vetter" <daniel@ffwll.ch>,
	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-20220811 due to b1a63a0b48ad ("drm/amd/display: consider DSC pass-through during mode validation")
Date: Thu, 11 Aug 2022 18:10:48 +0100	[thread overview]
Message-ID: <YvU4GD8HtZ1A4dhI@debian> (raw)

Hi All,

Not sure if it has been reported, builds of riscv, alpha, s390, arm,
arm64, xtensa, mips, csky allmodconfig have failed to build next-20220811
with the error:

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

git bisect pointed to b1a63a0b48ad ("drm/amd/display: consider DSC pass-through during mode validation")
And, reverting that commit has fixed the build failure.

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>,
	Hamza Mahfooz <hamza.mahfooz@amd.com>,
	Fangzhi Zuo <Jerry.Zuo@amd.com>
Cc: "David Airlie" <airlied@linux.ie>,
	"Pan, Xinhui" <Xinhui.Pan@amd.com>,
	linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
	linux-next@vger.kernel.org, amd-gfx@lists.freedesktop.org,
	"Christian König" <christian.koenig@amd.com>
Subject: build failure of next-20220811 due to b1a63a0b48ad ("drm/amd/display: consider DSC pass-through during mode validation")
Date: Thu, 11 Aug 2022 18:10:48 +0100	[thread overview]
Message-ID: <YvU4GD8HtZ1A4dhI@debian> (raw)

Hi All,

Not sure if it has been reported, builds of riscv, alpha, s390, arm,
arm64, xtensa, mips, csky allmodconfig have failed to build next-20220811
with the error:

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

git bisect pointed to b1a63a0b48ad ("drm/amd/display: consider DSC pass-through during mode validation")
And, reverting that commit has fixed the build failure.

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


--
Regards
Sudip

             reply	other threads:[~2022-08-11 17:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 17:10 Sudip Mukherjee (Codethink) [this message]
2022-08-11 17:10 ` build failure of next-20220811 due to b1a63a0b48ad ("drm/amd/display: consider DSC pass-through during mode validation") Sudip Mukherjee (Codethink)
2022-08-11 17:10 ` Sudip Mukherjee (Codethink)
2022-08-11 17:16 ` Alex Deucher
2022-08-11 17:16   ` Alex Deucher
2022-08-11 17:37   ` Sudip Mukherjee
2022-08-11 17:37     ` Sudip Mukherjee
2022-08-11 17:57     ` [PATCH v2] drm/amd/display: fix DSC related non-x86/PPC64 compilation issue Hamza Mahfooz
2022-08-11 17:57       ` Hamza Mahfooz
2022-08-11 17:57       ` Hamza Mahfooz
2022-08-11 18:11       ` Sudip Mukherjee
2022-08-11 18:11         ` Sudip Mukherjee
2022-08-11 18:11         ` Sudip Mukherjee
2022-08-11 18:26       ` Anders Roxell
2022-08-11 18:26         ` Anders Roxell
2022-08-11 18:26         ` Anders Roxell
2022-08-11 18:34       ` Alex Deucher
2022-08-11 18:34         ` Alex Deucher
2022-08-11 18:34         ` Alex Deucher
2022-08-11 23:07 ` build failure of next-20220811 due to b1a63a0b48ad ("drm/amd/display: consider DSC pass-through during mode validation") Stephen Rothwell
2022-08-11 23:07   ` Stephen Rothwell
2022-08-11 23:07   ` Stephen Rothwell
2022-08-16 23:43   ` Stephen Rothwell
2022-08-16 23:43     ` Stephen Rothwell
2022-08-16 23:43     ` Stephen Rothwell
2022-08-17 20:39     ` Sudip Mukherjee
2022-08-17 20:39       ` Sudip Mukherjee
2022-08-17 20:39       ` Sudip Mukherjee
2022-08-17 22:11       ` Stephen Rothwell
2022-08-17 22:11         ` Stephen Rothwell
2022-08-17 22:11         ` Stephen Rothwell

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=YvU4GD8HtZ1A4dhI@debian \
    --to=sudipm.mukherjee@gmail.com \
    --cc=Jerry.Zuo@amd.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=hamza.mahfooz@amd.com \
    --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.