From: Jiri Kosina <jkosina@suse.cz>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Kosina <jikos@jikos.cz>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (hid tree related)
Date: Thu, 16 Aug 2012 12:05:57 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1208161204520.7026@pobox.suse.cz> (raw)
In-Reply-To: <20120816152538.7f850ee1a3b8ce90d9f749a2@canb.auug.org.au>
On Thu, 16 Aug 2012, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/hid/hid-picolcd_fb.c: In function 'picolcd_fb_destroy':
> drivers/hid/hid-picolcd_fb.c:350:2: error: implicit declaration of function 'vfree' [-Werror=implicit-function-declaration]
> drivers/hid/hid-picolcd_fb.c: In function 'picolcd_init_framebuffer':
> drivers/hid/hid-picolcd_fb.c:508:2: error: implicit declaration of function 'vmalloc' [-Werror=implicit-function-declaration]
> drivers/hid/hid-picolcd_fb.c:508:12: warning: assignment makes pointer from integer without a cast [enabled by default]
>
> Caused by commit fabdbf2fd22f ("HID: picoLCD: split driver code") from
> the hid tree.
Hmm, seems config dependent, doesn't trigger here. Probably vmalloc.h gets
sucked in some other way under certain config options.
Anyway I have now applied your patch Stephen, so you should be able to
drop it from your pile.
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2012-08-16 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 5:25 linux-next: build failure after merge of the final tree (hid tree related) Stephen Rothwell
2012-08-16 10:05 ` Jiri Kosina [this message]
2012-08-16 11:14 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-04-01 6:06 Stephen Rothwell
2010-04-01 6:18 ` Jiri Kosina
2010-04-01 7:35 ` Stephen Rothwell
2010-04-01 7:53 ` Bruno Prémont
2010-04-01 19:05 ` Bruno Prémont
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=alpine.LNX.2.00.1208161204520.7026@pobox.suse.cz \
--to=jkosina@suse.cz \
--cc=jikos@jikos.cz \
--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;
as well as URLs for NNTP newsgroup(s).