From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Simona Vetter <simona.vetter@ffwll•ch>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro•org>,
Maxime Ripard <mripard@kernel•org>,
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-misc-fixes tree
Date: Wed, 11 Sep 2024 18:07:41 +1000 [thread overview]
Message-ID: <20240911180741.45311006@canb.auug.org.au> (raw)
In-Reply-To: <20240904163018.214efaa7@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
Hi all,
On Wed, 4 Sep 2024 16:30:18 +1000 Stephen Rothwell <sfr@canb•auug.org.au> wrote:
>
> After merging the drm-misc-fixes tree, today's linux-next build (htmldocs)
> produced this warning:
>
> Error: Cannot open file drivers/gpu/drm/drm_bridge_connector.c
>
> Introduced by commit
>
> 9da7ec9b19d8 ("drm/bridge-connector: move to DRM_DISPLAY_HELPER module")
That commit is now in Linus' tree, but I am still getting the warning.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-09-11 8:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 6:30 linux-next: build warning after merge of the drm-misc-fixes tree Stephen Rothwell
2024-09-11 8:07 ` Stephen Rothwell [this message]
2024-09-12 8:49 ` Maxime Ripard
2024-09-12 13:57 ` Dmitry Baryshkov
-- strict thread matches above, loose matches on Subject: below --
2023-10-05 4:01 Stephen Rothwell
2020-11-03 0:31 Stephen Rothwell
2020-11-03 9:36 ` Maxime Ripard
2019-10-21 21:07 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=20240911180741.45311006@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=dmitry.baryshkov@linaro$(echo .)org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mripard@kernel$(echo .)org \
--cc=simona.vetter@ffwll$(echo .)ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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