From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Pan, Xinhui" <Xinhui.Pan@amd.com>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Jun 15 (drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c)
Date: Wed, 15 Jun 2022 12:01:08 -0700 [thread overview]
Message-ID: <d1a48a84-6d07-e8f7-5fd8-d24a7a1cf187@infradead.org> (raw)
In-Reply-To: <20220615160116.528c324b@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
On 6/14/22 23:01, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20220614:
>
on i386:
# CONFIG_DEBUG_FS is not set
../drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c: In function ‘amdgpu_dm_crtc_late_register’:
../drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:6599:2: error: implicit declaration of function ‘crtc_debugfs_init’; did you mean ‘amdgpu_debugfs_init’? [-Werror=implicit-function-declaration]
crtc_debugfs_init(crtc);
^~~~~~~~~~~~~~~~~
amdgpu_debugfs_init
Full randconfig file is attached.
--
~Randy
[-- Attachment #2: config-amdgpu-not-debugfs.gz --]
[-- Type: application/gzip, Size: 53827 bytes --]
next prev parent reply other threads:[~2022-06-15 19:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 6:01 linux-next: Tree for Jun 15 Stephen Rothwell
2022-06-15 16:28 ` linux-next: Tree for Jun 15 (drivers/dma/apple-admac.c) Randy Dunlap
2022-06-15 17:10 ` Arnd Bergmann
2022-06-15 17:23 ` Martin Povišer
2022-06-15 19:01 ` Randy Dunlap [this message]
2022-06-15 19:28 ` linux-next: Tree for Jun 15 (drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c) Alex Deucher
2022-06-15 19:44 ` Randy Dunlap
2022-06-15 20:13 ` Alex Deucher
2022-06-15 20:27 ` Randy Dunlap
2022-06-15 20:24 ` Nathan Chancellor
2022-06-15 20:45 ` Alex Deucher
2022-06-15 20:52 ` Nathan Chancellor
2022-06-15 23:26 ` Stephen Rothwell
2022-06-16 2:34 ` Alex Deucher
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=d1a48a84-6d07-e8f7-5fd8-d24a7a1cf187@infradead.org \
--to=rdunlap@infradead.org \
--cc=Xinhui.Pan@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®