diff options
| author | Javier Martinez Canillas <[email protected]> | 2022-06-10 08:54:50 +0000 |
|---|---|---|
| committer | Javier Martinez Canillas <[email protected]> | 2022-06-13 17:21:12 +0000 |
| commit | 0d4e57e5af39fef28de6c89b0b97741dedb4b72f (patch) | |
| tree | 3b5bbb6f1a732a9e9c224d849f3d498aeec3f8a1 /drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | |
| parent | drm/msm: Fix convert to drm_of_get_data_lanes_count (diff) | |
| download | kernel-0d4e57e5af39fef28de6c89b0b97741dedb4b72f.tar.gz kernel-0d4e57e5af39fef28de6c89b0b97741dedb4b72f.zip | |
Revert "fbdev: vesafb: Allow to be built if COMPILE_TEST is enabled"
This reverts commit fa0e256450f27a7d85f65c63f05e6897954a1d53. The kernel
test robot reported that attempting to build the vesafb driver fails on
some architectures, because these don't define a `struct screen_info`.
This leads to linking errors, for example on parisc with allyesconfig:
hppa-linux-ld: drivers/video/fbdev/vesafb.o: in function `vesafb_probe':
>> (.text+0x738): undefined reference to `screen_info'
>> hppa-linux-ld: (.text+0x73c): undefined reference to `screen_info'
hppa-linux-ld: drivers/firmware/sysfb.o: in function `sysfb_init':
>> (.init.text+0x28): undefined reference to `screen_info'
>> hppa-linux-ld: (.init.text+0x30): undefined reference to `screen_info'
hppa-linux-ld: (.init.text+0x78): undefined reference to `screen_info'
The goal of commit fa0e256450f2 ("fbdev: vesafb: Allow to be built if
COMPILE_TEST is enabled") was to have more build coverage for the driver
but it wrongly assumed that all architectures would define a screen_info.
Reported-by: kernel test robot <[email protected]>
Signed-off-by: Javier Martinez Canillas <[email protected]>
Acked-by: Daniel Vetter <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/[email protected]
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_object.c')
0 files changed, 0 insertions, 0 deletions
