From: Randy Dunlap <rdunlap@infradead.org>
To: Anders Roxell <anders.roxell@linaro.org>,
tomi.valkeinen@ti.com, b.zolnierkie@samsung.com
Cc: linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drivers: omap2: Kconfig: make FB_OMAP2_DSS_INIT depend on OF
Date: Thu, 03 May 2018 15:48:56 +0000 [thread overview]
Message-ID: <16e74acc-1265-faec-0c36-49681a7760e4@infradead.org> (raw)
In-Reply-To: <20180420112551.27027-1-anders.roxell@linaro.org>
On 04/20/2018 04:25 AM, Anders Roxell wrote:
> Commit 7378f1149884 ("media: omap2: omapfb: allow building it with
> COMPILE_TEST") broke compilation without CONFIG_OF selected.
> CC drivers/video/fbdev/core/fbmem.o
> drivers/video/fbdev/omap2/omapfb/dss/omapdss-boot-init.c: In function ‘omapdss_update_prop’:
> drivers/video/fbdev/omap2/omapfb/dss/omapdss-boot-init.c:68:2: error: implicit declaration of function ‘of_update_property’; did you mean ‘of_get_property’? [-Werror=implicit-function-declaration]
> of_update_property(node, prop);
> ^~~~~~~~~~~~~~~~~~
> of_get_property
> cc1: some warnings being treated as errors
> scripts/Makefile.build:312: recipe for target 'drivers/video/fbdev/omap2/omapfb/dss/omapdss-boot-init.o' failed
> make[7]: *** [drivers/video/fbdev/omap2/omapfb/dss/omapdss-boot-init.o] Error 1
> scripts/Makefile.build:559: recipe for target 'drivers/video/fbdev/omap2/omapfb/dss' failed
> make[6]: *** [drivers/video/fbdev/omap2/omapfb/dss] Error 2
> make[6]: *** Waiting for unfinished jobs....
>
> Add OF dependency in order to make all configurations work again.
>
> of_update_property() has no inline stub, and that that could be added as
> an alternative.
>
> Signed-off-by: Anders Roxell <anders.roxell@linaro.org>
> ---
> drivers/video/fbdev/omap2/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/video/fbdev/omap2/Kconfig b/drivers/video/fbdev/omap2/Kconfig
> index 82008699d253..4de381f2452e 100644
> --- a/drivers/video/fbdev/omap2/Kconfig
> +++ b/drivers/video/fbdev/omap2/Kconfig
> @@ -1,4 +1,4 @@
> -if ARCH_OMAP2PLUS || COMPILE_TEST
> +if OF && (ARCH_OMAP2PLUS || COMPILE_TEST)
>
> source "drivers/video/fbdev/omap2/omapfb/Kconfig"
>
>
Hi,
This patch certainly fixes the build errors that I have been seeing in
linux-next for several days now, so:
Acked-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
OTOH, I would rather see the Kconfig dependencies all expressed in
drivers/video/fbdev/omap2/omapfb/Kconfig instead of them being split
between 2 Kconfig files.
thanks,
--
~Randy
next prev parent reply other threads:[~2018-05-03 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 11:25 [PATCH] drivers: omap2: Kconfig: make FB_OMAP2_DSS_INIT depend on OF Anders Roxell
2018-05-03 15:48 ` Randy Dunlap [this message]
2018-05-04 10:48 ` Bartlomiej Zolnierkiewicz
2018-05-04 10:59 ` Mauro Carvalho Chehab
2018-05-04 11:05 ` Bartlomiej Zolnierkiewicz
2018-05-04 12:45 ` Mauro Carvalho Chehab
2018-05-04 12:57 ` Bartlomiej Zolnierkiewicz
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=16e74acc-1265-faec-0c36-49681a7760e4@infradead.org \
--to=rdunlap@infradead.org \
--cc=anders.roxell@linaro.org \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=tomi.valkeinen@ti.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