From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2 15/19] omap2: omapfb: allow building it with COMPILE_TEST
Date: Fri, 20 Apr 2018 15:13:17 +0000 [thread overview]
Message-ID: <3329803.Cv7XkTmsQk@amdc3058> (raw)
In-Reply-To: <f0947227675df4a774949500b6ee4cac1485b494.1522959716.git.mchehab@s-opensource.com>
On Thursday, April 05, 2018 04:29:42 PM Mauro Carvalho Chehab wrote:
> This driver builds cleanly with COMPILE_TEST, and it is
> needed in order to allow building drivers/media omap2
> driver.
>
> So, change the logic there to allow building it.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
This change has broken build on OF=n && COMPILE_TEST=y configs:
https://patchwork.kernel.org/patch/10352465/
[ This is not a problem when compiling for OMAP2 because it depends
on ARM Multiplatform support which (indirectly) selects OF. ]
Also I would really prefer that people won't merge fbdev related
patches without my ACK and I see this patch in -next coming from
one of your trees..
> ---
> 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 0921c4de8407..82008699d253 100644
> --- a/drivers/video/fbdev/omap2/Kconfig
> +++ b/drivers/video/fbdev/omap2/Kconfig
> @@ -1,4 +1,4 @@
> -if ARCH_OMAP2PLUS
> +if ARCH_OMAP2PLUS || COMPILE_TEST
>
> source "drivers/video/fbdev/omap2/omapfb/Kconfig"
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
WARNING: multiple messages have this Message-ID (diff)
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap@vger.kernel.org,
Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH v2 15/19] omap2: omapfb: allow building it with COMPILE_TEST
Date: Fri, 20 Apr 2018 17:13:17 +0200 [thread overview]
Message-ID: <3329803.Cv7XkTmsQk@amdc3058> (raw)
In-Reply-To: <f0947227675df4a774949500b6ee4cac1485b494.1522959716.git.mchehab@s-opensource.com>
On Thursday, April 05, 2018 04:29:42 PM Mauro Carvalho Chehab wrote:
> This driver builds cleanly with COMPILE_TEST, and it is
> needed in order to allow building drivers/media omap2
> driver.
>
> So, change the logic there to allow building it.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
This change has broken build on OF=n && COMPILE_TEST=y configs:
https://patchwork.kernel.org/patch/10352465/
[ This is not a problem when compiling for OMAP2 because it depends
on ARM Multiplatform support which (indirectly) selects OF. ]
Also I would really prefer that people won't merge fbdev related
patches without my ACK and I see this patch in -next coming from
one of your trees..
> ---
> 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 0921c4de8407..82008699d253 100644
> --- a/drivers/video/fbdev/omap2/Kconfig
> +++ b/drivers/video/fbdev/omap2/Kconfig
> @@ -1,4 +1,4 @@
> -if ARCH_OMAP2PLUS
> +if ARCH_OMAP2PLUS || COMPILE_TEST
>
> source "drivers/video/fbdev/omap2/omapfb/Kconfig"
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-omap@vger.kernel.org, linux-fbdev@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 15/19] omap2: omapfb: allow building it with COMPILE_TEST
Date: Fri, 20 Apr 2018 17:13:17 +0200 [thread overview]
Message-ID: <3329803.Cv7XkTmsQk@amdc3058> (raw)
In-Reply-To: <f0947227675df4a774949500b6ee4cac1485b494.1522959716.git.mchehab@s-opensource.com>
On Thursday, April 05, 2018 04:29:42 PM Mauro Carvalho Chehab wrote:
> This driver builds cleanly with COMPILE_TEST, and it is
> needed in order to allow building drivers/media omap2
> driver.
>
> So, change the logic there to allow building it.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
This change has broken build on OF=n && COMPILE_TEST=y configs:
https://patchwork.kernel.org/patch/10352465/
[ This is not a problem when compiling for OMAP2 because it depends
on ARM Multiplatform support which (indirectly) selects OF. ]
Also I would really prefer that people won't merge fbdev related
patches without my ACK and I see this patch in -next coming from
one of your trees..
> ---
> 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 0921c4de8407..82008699d253 100644
> --- a/drivers/video/fbdev/omap2/Kconfig
> +++ b/drivers/video/fbdev/omap2/Kconfig
> @@ -1,4 +1,4 @@
> -if ARCH_OMAP2PLUS
> +if ARCH_OMAP2PLUS || COMPILE_TEST
>
> source "drivers/video/fbdev/omap2/omapfb/Kconfig"
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
next prev parent reply other threads:[~2018-04-20 15:13 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 20:29 [PATCH v2 00/19] Make all media drivers build with COMPILE_TEST Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 01/19] omap: omap-iommu.h: allow building drivers " Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 02/19] media: omap3isp: allow it to build " Mauro Carvalho Chehab
2018-04-06 12:56 ` kbuild test robot
2018-04-07 13:31 ` Laurent Pinchart
2018-04-05 20:29 ` [PATCH v2 03/19] media: omap3isp/isp: remove an unused static var Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 04/19] media: fsl-viu: mark static functions as such Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 05/19] media: fsl-viu: allow building it with COMPILE_TEST Mauro Carvalho Chehab
2018-04-06 10:43 ` kbuild test robot
2018-04-06 14:03 ` kbuild test robot
2018-04-05 20:29 ` [PATCH v2 06/19] media: cec_gpio: allow building CEC_GPIO " Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 07/19] media: exymos4-is: allow compile test for EXYNOS FIMC-LITE Mauro Carvalho Chehab
2018-04-05 20:29 ` Mauro Carvalho Chehab
2018-04-05 20:29 ` Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 08/19] media: mmp-camera.h: add missing platform data Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 09/19] media: marvel-ccic: re-enable mmp-driver build Mauro Carvalho Chehab
2018-04-06 14:52 ` kbuild test robot
2018-04-05 20:29 ` [PATCH v2 10/19] media: mmp-driver: make two functions static Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 11/19] media: davinci: allow building isif code Mauro Carvalho Chehab
2018-04-06 16:17 ` kbuild test robot
2018-04-05 20:29 ` [PATCH v2 12/19] media: davinci: allow build vpbe_display with COMPILE_TEST Mauro Carvalho Chehab
2018-04-06 18:08 ` kbuild test robot
2018-04-05 20:29 ` [PATCH v2 13/19] media: vpbe_venc: don't store return codes if they won't be used Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 14/19] media: davinci: get rid of lots of kernel-doc warnings Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 15/19] omap2: omapfb: allow building it with COMPILE_TEST Mauro Carvalho Chehab
2018-04-05 20:29 ` Mauro Carvalho Chehab
2018-04-05 20:29 ` Mauro Carvalho Chehab
2018-04-06 8:41 ` Tomi Valkeinen
2018-04-06 8:41 ` Tomi Valkeinen
2018-04-06 8:41 ` Tomi Valkeinen
2018-04-06 11:46 ` kbuild test robot
2018-04-06 11:46 ` kbuild test robot
2018-04-06 11:46 ` kbuild test robot
2018-04-06 19:29 ` kbuild test robot
2018-04-06 19:29 ` kbuild test robot
2018-04-06 19:29 ` kbuild test robot
2018-04-20 15:13 ` Bartlomiej Zolnierkiewicz [this message]
2018-04-20 15:13 ` Bartlomiej Zolnierkiewicz
2018-04-20 15:13 ` Bartlomiej Zolnierkiewicz
2018-04-05 20:29 ` [PATCH v2 16/19] media: omap: " Mauro Carvalho Chehab
2018-04-06 12:11 ` kbuild test robot
2018-04-05 20:29 ` [PATCH v2 17/19] media: omap4iss: make it build " Mauro Carvalho Chehab
2018-04-05 20:59 ` Laurent Pinchart
2018-04-05 20:29 ` [PATCH v2 18/19] media: si470x: allow build both USB and I2C at the same time Mauro Carvalho Chehab
2018-04-06 16:21 ` kbuild test robot
2018-04-06 16:46 ` Mauro Carvalho Chehab
2018-04-18 17:07 ` Daniel Scheller
2018-04-18 18:53 ` Mauro Carvalho Chehab
2018-04-18 19:06 ` Daniel Scheller
2018-04-18 19:17 ` Mauro Carvalho Chehab
2018-04-05 20:29 ` [PATCH v2 19/19] media: staging: davinci_vpfe: allow building with COMPILE_TEST Mauro Carvalho Chehab
2018-04-06 22:25 ` kbuild test robot
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=3329803.Cv7XkTmsQk@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mchehab@s-opensource.com \
--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 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.