[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <51030f00-48c6-49b6-a4be-0b4e238f71bd@gmail.com>
Date: Mon, 6 Oct 2025 09:49:48 -0400
From: David Hunter <david.hunter.linux@...il.com>
To: sukrut heroorkar <hsukrut3@...il.com>
Cc: kernel test robot <lkp@...el.com>, Helge Deller <deller@....de>,
Bernie Thompson <bernie@...gable.com>,
Thomas Zimmermann <tzimmermann@...e.de>, Arnd Bergmann <arnd@...db.de>,
Randy Dunlap <rdunlap@...radead.org>,
Bartosz Golaszewski <bartosz.golaszewski@...aro.org>,
Zsolt Kajtar <soci@....rulez.org>,
Gonzalo Silvalde Blanco <gonzalo.silvalde@...il.com>,
linux-fbdev@...r.kernel.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, llvm@...ts.linux.dev,
oe-kbuild-all@...ts.linux.dev, skhan@...uxfoundation.org
Subject: Re: [PATCH] fbdev: udlfb: make CONFIG_FB_DEVICE optional
On 10/2/25 02:35, sukrut heroorkar wrote:
>>> kernel test robot noticed the following build errors:
>>>
>> Did you compile and test this code before submitting this patch?
>>
>>
> Yes, I had compiled & loaded the udlfb module with no errors. Please
> let me know how to proceed
> in this case.
Hey Sukrut,
When you make code that deletes something from the kernel, you need to
make sure that all other code that references that code will still
function properly.
When you surround things in the #ifdev, depending on the config file,
the compiler strips those things out and compiles without them. That
means that you actually need to compile and test under two conditions.
Once when CONFIG_FB_DEVICE=y and another time when CONFIG_FB_DEVICE=n.
The test robot gave you a sample config file that you can use. Please
ensure that you have the proper version of Clang on your Host machine
for that particular config file, if you choose to use it.
Also, I strongly recommend that you run the code on a sufficient
hardware or emulator after you test it so that you can verify that the
code does what you think it does.
Thanks,
David Hunter
Powered by blists - more mailing lists