[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3006e72e-fde0-127c-bd59-3902032a0c18@samsung.com>
Date: Wed, 29 Apr 2020 15:14:41 +0200
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Stephen Rothwell <sfr@...b.auug.org.au>,
kbuild test robot <lkp@...el.com>,
Sam Ravnborg <sam@...nborg.org>,
Daniel Vetter <daniel.vetter@...ll.ch>,
linux-fbdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] video: fbdev: controlfb: fix build for
COMPILE_TEST=y && PPC_PMAC=y && PPC32=n
On 4/29/20 2:51 PM, Christoph Hellwig wrote:
> Why do we even bother allocing the driver to compile for !ppc32
> given that it clearly needs ppc-specific infrastructure? The whole
> idea of needing magic stubs for the COMPILE_TEST case seems rather
> counterproduction.
Not a perfect solution but at the cost of 2 ifdefs it allows controlfb
driver to be compile tested on any arch.
Being able to compile test fbdev device drivers is really useful for
me and saves me a lot of time when doing fbdev maintainer duties.
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
Powered by blists - more mailing lists