From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-fbdev@vger.kernel.org, Dave Airlie <airlied@gmail.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Rob Clark <robdclark@gmail.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAPDSS: fix omapfb build error due missing feat functions declaration
Date: Tue, 22 Dec 2015 07:50:21 +0000 [thread overview]
Message-ID: <567900BD.6070907@ti.com> (raw)
In-Reply-To: <1450722384-4606-1-git-send-email-javier@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
Hi Javier,
On 21/12/15 20:26, Javier Martinez Canillas wrote:
> The omapfb is failing to build in -next due missing declarations for
> dss_feat_get_supported_displays() and dss_feat_get_supported_outputs():
>
> CC [M] drivers/video/fbdev/omap2//omapfb/dss/dss.o
> drivers/video/fbdev/omap2//omapfb/dss/dss.c: In function 'dss_save_context':
> drivers/video/fbdev/omap2//omapfb/dss/dss.c:144:2: error: implicit declaration of function 'dss_feat_get_supported_displays' [-Werror=implicit-function-declaration]
>
> Add the declaration for these functions in the dss_features.h header
> file to fix this compile error.
>
> Also, remove the functions export since are not used outside the driver.
Thanks!
Yep, I messed that up. I thought I had tested it, but apparently I only
tested the final for-next only for omapdrm, which does compile and work.
omapdss.h is the the only file still shared between omapdrm and omapfb
after the copy-omapdss-series (I'll work on omapdss.h later), and of
course there was a change to omapdss.h which broke the build.
So I rebased the copy-omapdss-series on top of the rest of the omapdss
patches, and updated the "omapfb: copy omapdss & displays for omapfb" to
make a fresh copy of omapdss for omapfb. I think it's better to update
the series, rather than applying fixes for already confusing series.
I've pushed new version to my for-next branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: Tony Lindgren <tony@atomide.com>,
linux-fbdev@vger.kernel.org, Dave Airlie <airlied@gmail.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Rob Clark <robdclark@gmail.com>,
linux-omap@vger.kernel.org
Subject: Re: [PATCH] OMAPDSS: fix omapfb build error due missing feat functions declaration
Date: Tue, 22 Dec 2015 09:50:21 +0200 [thread overview]
Message-ID: <567900BD.6070907@ti.com> (raw)
In-Reply-To: <1450722384-4606-1-git-send-email-javier@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
Hi Javier,
On 21/12/15 20:26, Javier Martinez Canillas wrote:
> The omapfb is failing to build in -next due missing declarations for
> dss_feat_get_supported_displays() and dss_feat_get_supported_outputs():
>
> CC [M] drivers/video/fbdev/omap2//omapfb/dss/dss.o
> drivers/video/fbdev/omap2//omapfb/dss/dss.c: In function 'dss_save_context':
> drivers/video/fbdev/omap2//omapfb/dss/dss.c:144:2: error: implicit declaration of function 'dss_feat_get_supported_displays' [-Werror=implicit-function-declaration]
>
> Add the declaration for these functions in the dss_features.h header
> file to fix this compile error.
>
> Also, remove the functions export since are not used outside the driver.
Thanks!
Yep, I messed that up. I thought I had tested it, but apparently I only
tested the final for-next only for omapdrm, which does compile and work.
omapdss.h is the the only file still shared between omapdrm and omapfb
after the copy-omapdss-series (I'll work on omapdss.h later), and of
course there was a change to omapdss.h which broke the build.
So I rebased the copy-omapdss-series on top of the rest of the omapdss
patches, and updated the "omapfb: copy omapdss & displays for omapfb" to
make a fresh copy of omapdss for omapfb. I think it's better to update
the series, rather than applying fixes for already confusing series.
I've pushed new version to my for-next branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
<linux-kernel@vger.kernel.org>
Cc: Tony Lindgren <tony@atomide.com>, <linux-fbdev@vger.kernel.org>,
Dave Airlie <airlied@gmail.com>,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Rob Clark <robdclark@gmail.com>, <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] OMAPDSS: fix omapfb build error due missing feat functions declaration
Date: Tue, 22 Dec 2015 09:50:21 +0200 [thread overview]
Message-ID: <567900BD.6070907@ti.com> (raw)
In-Reply-To: <1450722384-4606-1-git-send-email-javier@osg.samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1430 bytes --]
Hi Javier,
On 21/12/15 20:26, Javier Martinez Canillas wrote:
> The omapfb is failing to build in -next due missing declarations for
> dss_feat_get_supported_displays() and dss_feat_get_supported_outputs():
>
> CC [M] drivers/video/fbdev/omap2//omapfb/dss/dss.o
> drivers/video/fbdev/omap2//omapfb/dss/dss.c: In function 'dss_save_context':
> drivers/video/fbdev/omap2//omapfb/dss/dss.c:144:2: error: implicit declaration of function 'dss_feat_get_supported_displays' [-Werror=implicit-function-declaration]
>
> Add the declaration for these functions in the dss_features.h header
> file to fix this compile error.
>
> Also, remove the functions export since are not used outside the driver.
Thanks!
Yep, I messed that up. I thought I had tested it, but apparently I only
tested the final for-next only for omapdrm, which does compile and work.
omapdss.h is the the only file still shared between omapdrm and omapfb
after the copy-omapdss-series (I'll work on omapdss.h later), and of
course there was a change to omapdss.h which broke the build.
So I rebased the copy-omapdss-series on top of the rest of the omapdss
patches, and updated the "omapfb: copy omapdss & displays for omapfb" to
make a fresh copy of omapdss for omapfb. I think it's better to update
the series, rather than applying fixes for already confusing series.
I've pushed new version to my for-next branch.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-12-22 7:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-21 18:26 [PATCH] OMAPDSS: fix omapfb build error due missing feat functions declaration Javier Martinez Canillas
2015-12-21 18:26 ` Javier Martinez Canillas
2015-12-22 7:50 ` Tomi Valkeinen [this message]
2015-12-22 7:50 ` Tomi Valkeinen
2015-12-22 7:50 ` Tomi Valkeinen
2015-12-22 12:02 ` Javier Martinez Canillas
2015-12-22 12:02 ` Javier Martinez Canillas
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=567900BD.6070907@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=airlied@gmail.com \
--cc=javier@osg.samsung.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=plagnioj@jcrosoft.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.