From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: Bhawanpreet Lakha <Bhawanpreet.Lakha@amd.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Dave Airlie <airlied@linux.ie>,
DRI <dri-devel@lists.freedesktop.org>
Subject: linux-next: build warnings after merge of the amdgpu tree
Date: Mon, 11 Jan 2021 14:38:58 +1100 [thread overview]
Message-ID: <20210111143858.6fbaaf9a@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
Hi all,
After merging the amdgpu tree, today's linux-next build (htmldocs)
produced these warnings:
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:340: warning: Incorrect use of kernel-doc format: * @active_vblank_irq_count
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h:379: warning: Function parameter or member 'active_vblank_irq_count' not described in 'amdgpu_display_manager'
Introduced by commit
71338cb4a7c2 ("drm/amd/display: enable idle optimizations for linux (MALL stutter)")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-01-11 3:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 3:38 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-20 3:39 linux-next: build warnings after merge of the amdgpu tree Stephen Rothwell
2024-04-26 6:55 Stephen Rothwell
2024-04-26 7:20 ` Khatri, Sunil
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
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=20210111143858.6fbaaf9a@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Bhawanpreet.Lakha@amd.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).