Except for driver bugs (which we'll catch with a WARN_ON) this is only to report failures of the new driver taking over the console. There's nothing the outgoing driver can do about that, and no one ever bothered to actually look at these return values. So remove them all. v2: fixup unregister_framebuffer in savagefb, fbtft, ivtvfb, and neofb drivers, reported by kbuild.
Showing the changes to include/linux (1 of 6 files). Show all
Unified · Split
| @@ -634,8 +634,8 @@ extern ssize_t fb_sys_write(struct fb_info *info, const char __user *buf, · 633 unmodified lines | ||
| 634 | 634 | |
| 635 | 635 | /* drivers/video/fbmem.c */ |
| 636 | 636 | extern int register_framebuffer(struct fb_info *fb_info); |
| 637 | −extern int unregister_framebuffer(struct fb_info *fb_info); | |
| 638 | −extern int unlink_framebuffer(struct fb_info *fb_info); | |
| 637 | +extern void unregister_framebuffer(struct fb_info *fb_info); | |
| 638 | +extern void unlink_framebuffer(struct fb_info *fb_info); | |
| 639 | 639 | extern int remove_conflicting_pci_framebuffers(struct pci_dev *pdev, int res_id, |
| 640 | 640 | const char *name); |
| 641 | 641 | extern int remove_conflicting_framebuffers(struct apertures_struct *a, |