dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <treding@nvidia.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: rmk+kernel@arm.linux.org.uk, dri-devel@lists.freedesktop.org,
	Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH]  drm/bridge: Fix the dw_hdmi object name
Date: Fri, 14 Aug 2015 21:49:23 +0200	[thread overview]
Message-ID: <20150814194922.GA19392@ulmo.nvidia.com> (raw)
In-Reply-To: <1439561596-20825-1-git-send-email-festevam@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 819 bytes --]

On Fri, Aug 14, 2015 at 11:13:16AM -0300, Fabio Estevam wrote:
> From: Fabio Estevam <fabio.estevam@freescale.com>
> 
> Commit 66d5e6d329aed4 ("drm/bridge: Add vendor prefixes") changed
> the object name to dw-hdmi.o, which breaks the build:
> 
> make[4]: *** No rule to make target `drivers/gpu/drm/bridge/dw-hdmi.o', needed by `drivers/gpu/drm/bridge/built-in.o'.  Stop.
> 
> Fix it by using the correct 'dw_hdmi.o' name.
> 
> Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
> ---
>  drivers/gpu/drm/bridge/Makefile | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)

Urgh... that's left-over of a change I backed out to avoid any potential
conflicts with Russell's work on the dw-hdmi driver. I've updated the
branch with your fix and resent a new pull request.

Thanks,
Thierry

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2015-08-14 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 14:13 [PATCH] drm/bridge: Fix the dw_hdmi object name Fabio Estevam
2015-08-14 19:49 ` Thierry Reding [this message]

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=20150814194922.GA19392@ulmo.nvidia.com \
    --to=treding@nvidia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fabio.estevam@freescale.com \
    --cc=festevam@gmail.com \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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