From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
dri-devel <dri-devel@lists.freedesktop.org>,
Dave Airlie <airlied@redhat.com>
Subject: Re: linux-next: Tree for Jul 25 (drm/udl without CONFIG_FB)
Date: Mon, 25 Jul 2016 09:32:39 -0700 [thread overview]
Message-ID: <a3af152d-aec2-4cb7-4b2e-bd0856d96771@infradead.org> (raw)
In-Reply-To: <20160725161748.61523c10@canb.auug.org.au>
On 07/24/16 23:17, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20160724:
>
on i386, when CONFIG_FB is not enabled:
../drivers/gpu/drm/udl/udl_fb.c: In function 'udl_fb_open':
../drivers/gpu/drm/udl/udl_fb.c:206:23: error: 'struct fb_info' has no member named 'fbdefio'
if (fb_defio && (info->fbdefio == NULL)) {
^
../drivers/gpu/drm/udl/udl_fb.c:211:28: error: invalid application of 'sizeof' to incomplete type 'struct fb_deferred_io'
fbdefio = kmalloc(sizeof(struct fb_deferred_io), GFP_KERNEL);
^
../drivers/gpu/drm/udl/udl_fb.c:214:11: error: dereferencing pointer to incomplete type
fbdefio->delay = DL_DEFIO_WRITE_DELAY;
^
../drivers/gpu/drm/udl/udl_fb.c:215:11: error: dereferencing pointer to incomplete type
fbdefio->deferred_io = drm_fb_helper_deferred_io;
^
../drivers/gpu/drm/udl/udl_fb.c:218:7: error: 'struct fb_info' has no member named 'fbdefio'
info->fbdefio = fbdefio;
^
../drivers/gpu/drm/udl/udl_fb.c: In function 'udl_fb_release':
../drivers/gpu/drm/udl/udl_fb.c:238:38: error: 'struct fb_info' has no member named 'fbdefio'
if ((ufbdev->fb_count == 0) && (info->fbdefio)) {
^
../drivers/gpu/drm/udl/udl_fb.c:240:13: error: 'struct fb_info' has no member named 'fbdefio'
kfree(info->fbdefio);
^
../drivers/gpu/drm/udl/udl_fb.c:241:7: error: 'struct fb_info' has no member named 'fbdefio'
info->fbdefio = NULL;
^
--
~Randy
prev parent reply other threads:[~2016-07-25 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 6:17 linux-next: Tree for Jul 25 Stephen Rothwell
2016-07-25 16:32 ` Randy Dunlap [this message]
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=a3af152d-aec2-4cb7-4b2e-bd0856d96771@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®