From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Dave Airlie <airlied@redhat.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Maarten Lankhorst <maarten.lankhorst@intel.com>,
"Golani,
Mitulkumar Ajitkumar" <mitulkumar.ajitkumar.golani@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Suraj Kandpal <suraj.kandpal@intel.com>,
Intel Graphics <intel-gfx@lists.freedesktop.org>,
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 warning after merge of the drm-intel tree
Date: Tue, 30 Jul 2024 20:10:56 +1000 [thread overview]
Message-ID: <20240730201056.70f71496@canb.auug.org.au> (raw)
In-Reply-To: <679e9674-9611-48a8-8f94-4285b080d3f6@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
Hi all,
On Mon, 15 Jul 2024 14:13:37 +0200 Maarten Lankhorst <maarten.lankhorst@intel.com> wrote:
>
> Den 2024-07-15 kl. 06:21, skrev Golani, Mitulkumar Ajitkumar:
> >
> > On 15-07-2024 04:42, Stephen Rothwell wrote:
> >>
> >> On Wed, 12 Jun 2024 14:11:10 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >>> After merging the drm-intel tree, today's linux-next build (htmldocs)
> >>> produced this warning:
> >>>
> >>> include/drm/display/drm_dp_helper.h:127: warning: Function parameter or struct member 'target_rr_divider' not described in 'drm_dp_as_sdp'
> >>>
> >>> Introduced by commit
> >>>
> >>> a20c6d954d75 ("drm/dp: Add refresh rate divider to struct representing AS SDP")
> >> I am now seeing that warning after the merge of the drm tree.
> > Hi Stephen Rothwell,
> >
> > I have already floated changes : https://patchwork.freedesktop.org/patch/604143/?series=136072&rev=1
> >
> > Need help on Ack from drm-maintainers to merge.
>
> There you go, does it need to go through drm-misc too?
I am still seeing these warnings.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-07-30 10:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-12 4:11 linux-next: build warning after merge of the drm-intel tree Stephen Rothwell
2024-07-14 23:12 ` Stephen Rothwell
2024-07-15 4:21 ` Golani, Mitulkumar Ajitkumar
2024-07-15 12:13 ` Maarten Lankhorst
2024-07-30 10:10 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-01 3:43 Stephen Rothwell
2024-10-11 5:57 ` Stephen Rothwell
2024-04-18 6:38 Stephen Rothwell
2024-02-19 5:17 Stephen Rothwell
2023-11-14 3:17 Stephen Rothwell
2023-11-14 8:22 ` Jani Nikula
2023-11-14 8:53 ` Jani Nikula
2024-01-21 22:25 ` Stephen Rothwell
2024-01-22 17:22 ` Jani Nikula
2022-11-30 3:45 Stephen Rothwell
2015-05-07 5:29 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=20240730201056.70f71496@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maarten.lankhorst@intel.com \
--cc=mitulkumar.ajitkumar.golani@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=suraj.kandpal@intel.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