linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Ajay Kumar <ajaykumar.rs@samsung.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	Inki Dae <inki.dae@samsung.com>,
	Rahul Sharma <rahul.sharma@samsung.com>,
	Thierry Reding <treding@nvidia.com>
Subject: build fails: drm/bridge: make bridge registration independent of drm flow
Date: Wed, 28 Jan 2015 18:02:22 -0500	[thread overview]
Message-ID: <54C96A7E.2000207@windriver.com> (raw)

Hi Ajay,

While doing build testing of linux-next I got a build
failure.

I found that you'd removed a function in your commit
(see subject) but callers still exist:

$ git grep drm_bridge_cleanup
drivers/gpu/drm/bridge/dw_hdmi.c:       drm_bridge_cleanup(bridge);
drivers/gpu/drm/sti/sti_dvo.c:  drm_bridge_cleanup(bridge);
drivers/gpu/drm/sti/sti_dvo.c:  drm_bridge_cleanup(bridge);
$

You probably want to fix up those remaining files and resubmit.

Thanks,
Paul.


 

                 reply	other threads:[~2015-01-29  4:08 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=54C96A7E.2000207@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=ajaykumar.rs@samsung.com \
    --cc=inki.dae@samsung.com \
    --cc=linux-next@vger.kernel.org \
    --cc=rahul.sharma@samsung.com \
    --cc=treding@nvidia.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;
as well as URLs for NNTP newsgroup(s).