From: kernel test robot <lkp@intel.com>
To: Thomas Zimmermann <tzimmermann@suse.de>,
javierm@redhat.com, pjones@redhat.com, deller@gmx.de,
ardb@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>
Subject: Re: [PATCH v2 3/8] firmware/sysfb: Set firmware-framebuffer parent device
Date: Sun, 4 Feb 2024 03:12:30 +0800 [thread overview]
Message-ID: <202402040214.GFutmkRC-lkp@intel.com> (raw)
In-Reply-To: <20240202120140.3517-4-tzimmermann@suse.de>
Hi Thomas,
kernel test robot noticed the following build errors:
[auto build test ERROR on drm-misc/drm-misc-next]
[also build test ERROR on drm-tip/drm-tip linus/master v6.8-rc2 next-20240202]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Thomas-Zimmermann/video-Add-helpers-for-decoding-screen_info/20240202-200314
base: git://anongit.freedesktop.org/drm/drm-misc drm-misc-next
patch link: https://lore.kernel.org/r/20240202120140.3517-4-tzimmermann%40suse.de
patch subject: [PATCH v2 3/8] firmware/sysfb: Set firmware-framebuffer parent device
config: i386-buildonly-randconfig-002-20240203 (https://download.01.org/0day-ci/archive/20240204/202402040214.GFutmkRC-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240204/202402040214.GFutmkRC-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202402040214.GFutmkRC-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/firmware/sysfb.c: In function 'sysfb_init':
>> drivers/firmware/sysfb.c:104:8: error: too many arguments to function 'sysfb_create_simplefb'
pd = sysfb_create_simplefb(si, &mode, parent);
^~~~~~~~~~~~~~~~~~~~~
In file included from drivers/firmware/sysfb.c:36:0:
include/linux/sysfb.h:105:39: note: declared here
static inline struct platform_device *sysfb_create_simplefb(const struct screen_info *si,
^~~~~~~~~~~~~~~~~~~~~
vim +/sysfb_create_simplefb +104 drivers/firmware/sysfb.c
83
84 static __init int sysfb_init(void)
85 {
86 struct screen_info *si = &screen_info;
87 struct device *parent;
88 struct simplefb_platform_data mode;
89 const char *name;
90 bool compatible;
91 int ret = 0;
92
93 mutex_lock(&disable_lock);
94 if (disabled)
95 goto unlock_mutex;
96
97 sysfb_apply_efi_quirks();
98
99 parent = sysfb_parent_dev(si);
100
101 /* try to create a simple-framebuffer device */
102 compatible = sysfb_parse_mode(si, &mode);
103 if (compatible) {
> 104 pd = sysfb_create_simplefb(si, &mode, parent);
105 if (!IS_ERR(pd))
106 goto unlock_mutex;
107 }
108
109 /* if the FB is incompatible, create a legacy framebuffer device */
110 if (si->orig_video_isVGA == VIDEO_TYPE_EFI)
111 name = "efi-framebuffer";
112 else if (si->orig_video_isVGA == VIDEO_TYPE_VLFB)
113 name = "vesa-framebuffer";
114 else if (si->orig_video_isVGA == VIDEO_TYPE_VGAC)
115 name = "vga-framebuffer";
116 else if (si->orig_video_isVGA == VIDEO_TYPE_EGAC)
117 name = "ega-framebuffer";
118 else
119 name = "platform-framebuffer";
120
121 pd = platform_device_alloc(name, 0);
122 if (!pd) {
123 ret = -ENOMEM;
124 goto unlock_mutex;
125 }
126
127 pd->dev.parent = parent;
128
129 sysfb_set_efifb_fwnode(pd);
130
131 ret = platform_device_add_data(pd, si, sizeof(*si));
132 if (ret)
133 goto err;
134
135 ret = platform_device_add(pd);
136 if (ret)
137 goto err;
138
139 goto unlock_mutex;
140 err:
141 platform_device_put(pd);
142 unlock_mutex:
143 mutex_unlock(&disable_lock);
144 return ret;
145 }
146
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-02-03 19:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 11:58 [PATCH v2 0/8] firmware/sysfb: Track parent device for screen_info Thomas Zimmermann
2024-02-02 11:58 ` [PATCH v2 1/8] video: Add helpers for decoding screen_info Thomas Zimmermann
2024-02-02 11:58 ` [PATCH v2 2/8] video: Provide screen_info_get_pci_dev() to find screen_info's PCI device Thomas Zimmermann
2024-02-02 16:31 ` [v2,2/8] " Sui Jingfeng
2024-02-05 8:14 ` Thomas Zimmermann
2024-02-02 17:03 ` Sui Jingfeng
2024-02-05 8:17 ` Thomas Zimmermann
2024-02-05 10:05 ` Sui Jingfeng
2024-02-05 12:32 ` Thomas Zimmermann
2024-02-04 1:53 ` [PATCH v2 2/8] " kernel test robot
2024-02-02 11:58 ` [PATCH v2 3/8] firmware/sysfb: Set firmware-framebuffer parent device Thomas Zimmermann
2024-02-02 14:40 ` [v2,3/8] " Sui Jingfeng
2024-02-02 15:23 ` Sui Jingfeng
2024-02-05 8:24 ` Thomas Zimmermann
2024-02-07 15:34 ` Sui Jingfeng
2024-02-03 19:12 ` kernel test robot [this message]
2024-02-04 2:13 ` [PATCH v2 3/8] " kernel test robot
2024-02-02 11:58 ` [PATCH v2 4/8] fbdev/efifb: Remove PM for " Thomas Zimmermann
2024-02-02 11:58 ` [PATCH v2 5/8] firmware/sysfb: Create firmware device only for enabled PCI devices Thomas Zimmermann
2024-02-02 17:50 ` [v2, " Sui Jingfeng
2024-02-05 8:25 ` Thomas Zimmermann
2024-02-02 11:58 ` [PATCH v2 6/8] fbdev/efifb: Do not track parent device status Thomas Zimmermann
2024-02-02 11:58 ` [PATCH v2 7/8] firmware/sysfb: Update screen_info for relocated EFI framebuffers Thomas Zimmermann
2024-02-02 17:54 ` [v2,7/8] " Sui Jingfeng
2024-02-05 10:11 ` Thomas Zimmermann
2024-02-02 18:00 ` Sui Jingfeng
2024-02-06 16:45 ` Thomas Zimmermann
2024-02-02 11:58 ` [PATCH v2 8/8] fbdev/efifb: Remove framebuffer relocation tracking Thomas Zimmermann
2024-02-02 18:07 ` [v2,8/8] " Sui Jingfeng
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202402040214.GFutmkRC-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb@kernel.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pjones@redhat.com \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).