From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
Sunil Khatri <sunil.khatri@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the amdgpu tree
Date: Fri, 26 Apr 2024 16:55:00 +1000 [thread overview]
Message-ID: <20240426165500.56c28076@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Hi all,
After merging the amdgpu tree, today's linux-next build (htmldocs)
produced these warnings:
drivers/gpu/drm/amd/include/amd_shared.h:327: warning: Function parameter or struct member 'dump_ip_state' not described in 'amd_ip_funcs'
drivers/gpu/drm/amd/include/amd_shared.h:327: warning: Function parameter or struct member 'print_ip_state' not described in 'amd_ip_funcs'
Introduced by commits
9c5c98ebec02 ("drm/amdgpu: add prototype for ip dump")
70977336d483 ("drm/amdgpu: add protype for print ip state")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2024-04-26 6:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 6:55 Stephen Rothwell [this message]
2024-04-26 7:20 ` linux-next: build warnings after merge of the amdgpu tree Khatri, Sunil
-- strict thread matches above, loose matches on Subject: below --
2024-01-30 2:49 Stephen Rothwell
2024-04-21 23:52 ` Stephen Rothwell
2023-07-11 23:08 Stephen Rothwell
2023-04-12 4:41 Stephen Rothwell
2023-03-16 1:18 Stephen Rothwell
2022-11-18 6:55 Stephen Rothwell
2023-07-11 23:15 ` Stephen Rothwell
2023-07-12 2:26 ` Randy Dunlap
2023-07-12 2:51 ` Stephen Rothwell
2022-08-11 2:10 Stephen Rothwell
2022-08-30 23:00 ` Stephen Rothwell
2022-10-05 0:34 ` Stephen Rothwell
2021-02-24 2:28 Stephen Rothwell
2021-02-24 4:09 ` Zhuo, Qingqing
2021-02-26 1:29 ` Stephen Rothwell
2021-01-11 3:38 Stephen Rothwell
2020-10-27 1:05 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=20240426165500.56c28076@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sunil.khatri@amd.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;
as well as URLs for NNTP newsgroup(s).