From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Dave Airlie <airlied@redhat.com>,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
DRI <dri-devel@lists.freedesktop.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warnings after merge of the amdgpu tree
Date: Wed, 12 Jul 2023 12:51:15 +1000 [thread overview]
Message-ID: <20230712125115.06caf01f@canb.auug.org.au> (raw)
In-Reply-To: <53602f8f-c37b-6570-d76d-5dd3c3329280@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 691 bytes --]
Hi Randy,
On Tue, 11 Jul 2023 19:26:33 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:
>
> On 7/11/23 16:15, Stephen Rothwell wrote:
> >
> > On Fri, 18 Nov 2022 17:55:45 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >>
> >> After merging the amdgpu tree, today's linux-next build (htmldocs)
> >> produced these warnings:
> >>
> >> drivers/gpu/drm/amd/display/dc/dc.h:548: warning: Function parameter or member 'dispclk_khz' not described in 'dc_clocks'
>
> This patch:
> https://lore.kernel.org/lkml/20230712022339.17902-1-rdunlap@infradead.org/T/#u
>
> removes all 175 kernel-doc warnings from dc.h.
Excellent, thanks.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-07-12 2:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 6:55 linux-next: build warnings after merge of the amdgpu tree Stephen Rothwell
2023-07-11 23:15 ` Stephen Rothwell
2023-07-12 2:26 ` Randy Dunlap
2023-07-12 2:51 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-20 3:39 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-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=20230712125115.06caf01f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Rodrigo.Siqueira@amd.com \
--cc=airlied@redhat.com \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@infradead.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).