From: Randy Dunlap <rd.dunlab@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-fbdev@vger.kernel.org, Helge Deller <deller@gmx.de>,
Javier Martinez Canillas <javierm@redhat.com>
Subject: Re: linux-next: Tree for Jul 18 (drivers/video/fbdev/ps3fb.c)
Date: Mon, 17 Jul 2023 22:24:21 -0700 [thread overview]
Message-ID: <84f0bdbc-09d1-ae4f-79ce-0d54c3410f18@gmail.com> (raw)
In-Reply-To: <20230718135733.0f1789a4@canb.auug.org.au>
Hi Thomas,
On 7/17/23 20:57, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20230717:
>
I'm still seeing build errors on PPC64 for ps3fb.c:
In file included from ../include/linux/device.h:15,
from ../arch/powerpc/include/asm/io.h:22,
from ../include/linux/io.h:13,
from ../include/linux/irq.h:20,
from ../arch/powerpc/include/asm/hardirq.h:6,
from ../include/linux/hardirq.h:11,
from ../include/linux/interrupt.h:11,
from ../drivers/video/fbdev/ps3fb.c:25:
../drivers/video/fbdev/ps3fb.c: In function 'ps3fb_probe':
../drivers/video/fbdev/ps3fb.c:1172:40: error: 'struct fb_info' has no member named 'dev'
1172 | dev_driver_string(info->dev), dev_name(info->dev),
| ^~
../include/linux/dev_printk.h:110:37: note: in definition of macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
../drivers/video/fbdev/ps3fb.c:1171:9: note: in expansion of macro 'dev_info'
1171 | dev_info(info->device, "%s %s, using %u KiB of video memory\n",
| ^~~~~~~~
../drivers/video/fbdev/ps3fb.c:1172:61: error: 'struct fb_info' has no member named 'dev'
1172 | dev_driver_string(info->dev), dev_name(info->dev),
| ^~
../include/linux/dev_printk.h:110:37: note: in definition of macro 'dev_printk_index_wrap'
110 | _p_func(dev, fmt, ##__VA_ARGS__); \
| ^~~~~~~~~~~
../drivers/video/fbdev/ps3fb.c:1171:9: note: in expansion of macro 'dev_info'
1171 | dev_info(info->device, "%s %s, using %u KiB of video memory\n",
| ^~~~~~~~
--
~Randy
parent reply other threads:[~2023-07-18 5:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20230718135733.0f1789a4@canb.auug.org.au>]
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=84f0bdbc-09d1-ae4f-79ce-0d54c3410f18@gmail.com \
--to=rd.dunlab@gmail.com \
--cc=deller@gmx.de \
--cc=javierm@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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).