[PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2"

2013-06-28 Thread Dave Airlie
On Fri, Jun 28, 2013 at 7:59 PM, Tomi Valkeinen wrote: > On 15/06/13 15:20, Rob Clark wrote: >> On Thu, Jun 13, 2013 at 6:31 AM, Paul Bolle wrote: >>> On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote: Signed-off-by: Paul Bolle --- Untested. Perhaps the first test that people

[PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2"

2013-06-28 Thread Tomi Valkeinen
On 15/06/13 15:20, Rob Clark wrote: > On Thu, Jun 13, 2013 at 6:31 AM, Paul Bolle wrote: >> On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote: >>> Signed-off-by: Paul Bolle >>> --- >>> Untested. Perhaps the first test that people with access to the relevant >>> hardware might do, is to test

Re: [PATCH] drm/omap: change !CONFIG_FB_OMAP2 to !FB_OMAP2

2013-06-28 Thread Dave Airlie
On Fri, Jun 28, 2013 at 7:59 PM, Tomi Valkeinen tomi.valkei...@iki.fi wrote: On 15/06/13 15:20, Rob Clark wrote: On Thu, Jun 13, 2013 at 6:31 AM, Paul Bolle pebo...@tiscali.nl wrote: On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote: Signed-off-by: Paul Bolle pebo...@tiscali.nl ---

Re: [PATCH] drm/omap: change !CONFIG_FB_OMAP2 to !FB_OMAP2

2013-06-28 Thread Tomi Valkeinen
On 15/06/13 15:20, Rob Clark wrote: On Thu, Jun 13, 2013 at 6:31 AM, Paul Bolle pebo...@tiscali.nl wrote: On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote: Signed-off-by: Paul Bolle pebo...@tiscali.nl --- Untested. Perhaps the first test that people with access to the relevant hardware

[PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2"

2013-06-15 Thread Thierry Reding
On Wed, Mar 13, 2013 at 08:48:22PM +0100, Paul Bolle wrote: > Signed-off-by: Paul Bolle > --- > Untested. Perhaps the first test that people with access to the relevant > hardware might do, is to test _before applying this patch_ with FB_OMAP2 > set. Perhaps this negative dependency isn't needed

[PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2"

2013-06-15 Thread Rob Clark
On Thu, Jun 13, 2013 at 6:31 AM, Paul Bolle wrote: > On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote: >> Signed-off-by: Paul Bolle >> --- >> Untested. Perhaps the first test that people with access to the relevant >> hardware might do, is to test _before applying this patch_ with FB_OMAP2 >>

Re: [PATCH] drm/omap: change !CONFIG_FB_OMAP2 to !FB_OMAP2

2013-06-15 Thread Thierry Reding
On Wed, Mar 13, 2013 at 08:48:22PM +0100, Paul Bolle wrote: Signed-off-by: Paul Bolle pebo...@tiscali.nl --- Untested. Perhaps the first test that people with access to the relevant hardware might do, is to test _before applying this patch_ with FB_OMAP2 set. Perhaps this negative dependency

Re: [PATCH] drm/omap: change !CONFIG_FB_OMAP2 to !FB_OMAP2

2013-06-15 Thread Rob Clark
On Thu, Jun 13, 2013 at 6:31 AM, Paul Bolle pebo...@tiscali.nl wrote: On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote: Signed-off-by: Paul Bolle pebo...@tiscali.nl --- Untested. Perhaps the first test that people with access to the relevant hardware might do, is to test _before applying

[PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2"

2013-06-13 Thread Paul Bolle
On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote: > Signed-off-by: Paul Bolle > --- > Untested. Perhaps the first test that people with access to the relevant > hardware might do, is to test _before applying this patch_ with FB_OMAP2 > set. Perhaps this negative dependency isn't needed at all.

Re: [PATCH] drm/omap: change !CONFIG_FB_OMAP2 to !FB_OMAP2

2013-06-13 Thread Paul Bolle
On Wed, 2013-03-13 at 20:48 +0100, Paul Bolle wrote: Signed-off-by: Paul Bolle pebo...@tiscali.nl --- Untested. Perhaps the first test that people with access to the relevant hardware might do, is to test _before applying this patch_ with FB_OMAP2 set. Perhaps this negative dependency isn't

[PATCH] drm/omap: change "!CONFIG_FB_OMAP2" to "!FB_OMAP2"

2013-03-13 Thread Paul Bolle
Signed-off-by: Paul Bolle --- Untested. Perhaps the first test that people with access to the relevant hardware might do, is to test _before applying this patch_ with FB_OMAP2 set. Perhaps this negative dependency isn't needed at all. Or is it obvious? drivers/gpu/drm/omapdrm/Kconfig | 2 +- 1

[PATCH] drm/omap: change !CONFIG_FB_OMAP2 to !FB_OMAP2

2013-03-13 Thread Paul Bolle
Signed-off-by: Paul Bolle pebo...@tiscali.nl --- Untested. Perhaps the first test that people with access to the relevant hardware might do, is to test _before applying this patch_ with FB_OMAP2 set. Perhaps this negative dependency isn't needed at all. Or is it obvious?