From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@redhat.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>,
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, 5 Oct 2022 11:34:11 +1100 [thread overview]
Message-ID: <20221005113411.0224d4a8@canb.auug.org.au> (raw)
In-Reply-To: <20220831090026.2e6b57ac@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
Hi all,
On Wed, 31 Aug 2022 09:00:26 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> On Thu, 11 Aug 2022 12:10:49 +1000 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:465: warning: Enum value 'MPC_SPLIT_AVOID' not described in enum 'pipe_split_policy'
> > drivers/gpu/drm/amd/display/dc/dc.h:465: warning: Enum value 'MPC_SPLIT_AVOID_MULT_DISP' not described in enum 'pipe_split_policy'
> >
> > Introduced by commit
> >
> > a2b3b9d57bdb ("drm/amd/display: Document pipe split policy")
>
> I am still seeing these warnings.
Still ...
This now commit
ea76895ffab1 ("drm/amd/display: Document pipe split policy")
in the drm tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-10-05 0:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-11 2:10 linux-next: build warnings after merge of the amdgpu tree Stephen Rothwell
2022-08-30 23:00 ` Stephen Rothwell
2022-10-05 0:34 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
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-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
2022-11-18 6:55 ` Stephen Rothwell
2023-07-11 23:15 ` Stephen Rothwell
2023-07-11 23:15 ` Stephen Rothwell
2023-07-12 2:26 ` Randy Dunlap
2023-07-12 2:26 ` Randy Dunlap
2023-07-12 2:51 ` Stephen Rothwell
2023-07-12 2:51 ` 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
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=20221005113411.0224d4a8@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Rodrigo.Siqueira@amd.com \
--cc=airlied@redhat.com \
--cc=alexdeucher@gmail.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.