Since commit b0e999c95581 ("fbdev: list all pci memory bars as conflicting apertures") the parameter was used for some sanity checks only, to make sure we detect any issues with the new approach to just list all memory bars as apertures. No issues turned up so far, so continue to cleanup: Drop the res_id parameter, drop the sanity checks. Also downgrade the logging from "info" level to "debug" level and update documentation.
Showing the changes to include/linux (1 of 3 files). Show all
Unified · Split
| @@ -607,7 +607,7 @@ extern ssize_t fb_sys_write(struct fb_info *info, const char __user *buf, · 606 unmodified lines | ||
| 607 | 607 | extern int register_framebuffer(struct fb_info *fb_info); |
| 608 | 608 | extern void unregister_framebuffer(struct fb_info *fb_info); |
| 609 | 609 | extern void unlink_framebuffer(struct fb_info *fb_info); |
| 610 | −extern int remove_conflicting_pci_framebuffers(struct pci_dev *pdev, int res_id, | |
| 610 | +extern int remove_conflicting_pci_framebuffers(struct pci_dev *pdev, | |
| 611 | 611 | const char *name); |
| 612 | 612 | extern int remove_conflicting_framebuffers(struct apertures_struct *a, |
| 613 | 613 | const char *name, bool primary); |