From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Jyri Sarha <jsarha@ti.com>
Cc: dri-devel@lists.freedesktop.org, airlied@linux.ie,
linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
bcousson@baylibre.com, tony@atomide.com,
rmk+kernel@arm.linux.org.uk, robdclark@gmail.com,
moinejf@free.fr
Subject: Re: [PATCH v2 6/7] drm/tilcdc: Force building of DRM_TILCDC_SLAVE_COMPAT
Date: Tue, 10 Mar 2015 13:40:09 +0200 [thread overview]
Message-ID: <54FED819.6070003@ti.com> (raw)
In-Reply-To: <59153f75fc48a34c9f36ebfdf7e6efe21bd03866.1425656120.git.jsarha@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1066 bytes --]
On 06/03/15 17:36, Jyri Sarha wrote:
> If I read Documentation/kbuild/makefiles.txt section 3.6 right, this
> patch should not be needed. However, without this patch the objects
> needed for DRM_TILCDC_SLAVE_COMPAT are not linked, if DRM_TILCDC is
> built as module.
>
> Signed-off-by: Jyri Sarha <jsarha@ti.com>
> ---
> drivers/gpu/drm/Makefile | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/Makefile b/drivers/gpu/drm/Makefile
> index 2c239b9..ad7f10f 100644
> --- a/drivers/gpu/drm/Makefile
> +++ b/drivers/gpu/drm/Makefile
> @@ -60,6 +60,7 @@ obj-$(CONFIG_DRM_RCAR_DU) += rcar-du/
> obj-$(CONFIG_DRM_SHMOBILE) +=shmobile/
> obj-$(CONFIG_DRM_OMAP) += omapdrm/
> obj-$(CONFIG_DRM_TILCDC) += tilcdc/
> +obj-$(CONFIG_DRM_TILCDC_SLAVE_COMPAT) += tilcdc/
> obj-$(CONFIG_DRM_QXL) += qxl/
> obj-$(CONFIG_DRM_BOCHS) += bochs/
> obj-$(CONFIG_DRM_MSM) += msm/
I don't think it's a good idea to enter the directory twice. Maybe it
works fine, I don't know, but I'd suggest just using "obj-y" above.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-10 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 15:36 [PATCH v2 0/7] Use DRM component API in tilcdc to connect to tda998x Jyri Sarha
2015-03-06 15:36 ` [PATCH v2 1/7] drm/tilcdc: Fix module unloading Jyri Sarha
2015-03-06 15:36 ` [PATCH v2 2/7] drm/tilcdc: Remove tilcdc slave support for tda998x driver Jyri Sarha
2015-03-06 15:36 ` [PATCH v2 3/7] drm/tilcdc: Add support for external tda998x encoder Jyri Sarha
2015-03-06 15:36 ` [PATCH v2 4/7] drm/tilcdc: Decrement refcount of ep-node from of_graph_get_next_endpoint Jyri Sarha
2015-03-06 15:36 ` [PATCH v2 5/7] drm/tilcdc: Add DRM_TILCDC_SLAVE_COMPAT for ti,tilcdc,slave binding support Jyri Sarha
2015-03-06 15:36 ` [PATCH v2 6/7] drm/tilcdc: Force building of DRM_TILCDC_SLAVE_COMPAT Jyri Sarha
2015-03-10 11:40 ` Tomi Valkeinen [this message]
2015-03-06 15:36 ` [PATCH v2 7/7] ARM: dts: am335x-boneblack: Use new binding for HDMI Jyri Sarha
2015-03-06 15:36 ` Tony Lindgren
2015-03-06 15:57 ` Jyri Sarha
[not found] ` <54F9CE53.908-l0cyMroinI0@public.gmane.org>
2015-03-06 16:58 ` Tony Lindgren
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=54FED819.6070003@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=airlied@linux.ie \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=robdclark@gmail.com \
--cc=tony@atomide.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).