From: Eric Anholt <eric@anholt.net>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Archit Taneja <architt@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v3] drm/bridge: Build the panel wrapper in drm_kms_helper
Date: Tue, 06 Jun 2017 10:52:55 -0700 [thread overview]
Message-ID: <87fufd9f60.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <3fd262cf-1db6-4335-320c-af92f9014502@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
Maarten Lankhorst <maarten.lankhorst@linux.intel.com> writes:
> This fixes the following depmod error when building drm as a module:
> depmod: ERROR: Found 6 modules in dependency cycles!
> depmod: ERROR: Cycle detected: drm -> drm_kms_helper -> drm
>
> Fixes: 13dfc0540a57 ("drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.")
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Looks plausible to me. Given how much trouble I've had getting the
kbuild right, anyone else want to chime in?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-06 17:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 20:25 [PATCH v3] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge Eric Anholt
2017-06-05 10:08 ` Archit Taneja
2017-06-06 14:24 ` Maarten Lankhorst
2017-06-06 14:31 ` [PATCH v3] drm/bridge: Build the panel wrapper in drm_kms_helper Maarten Lankhorst
2017-06-06 17:52 ` Eric Anholt [this message]
2017-06-07 8:19 ` Archit Taneja
2017-06-07 6:55 ` Lofstedt, Marta
2017-06-06 14:42 ` [PATCH v3] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge Thierry Reding
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=87fufd9f60.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=architt@codeaurora.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=thierry.reding@gmail.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