From: David Miller <davem@davemloft.net>
To: wei.liu2@citrix.com
Cc: arnd@arndb.de, netdev@vger.kernel.org,
andrew.bennieston@citrix.com, xen-devel@lists.xenproject.org,
jwboyer@fedoraproject.org
Subject: Re: [PATCH] net: xen-netback: include linux/vmalloc.h again
Date: Wed, 11 Jun 2014 15:19:01 -0700 (PDT) [thread overview]
Message-ID: <20140611.151901.986995853392690449.davem@davemloft.net> (raw)
In-Reply-To: <20140610084454.GB28084@zion.uk.xensource.com>
From: Wei Liu <wei.liu2@citrix.com>
Date: Tue, 10 Jun 2014 09:44:54 +0100
> On Tue, Jun 10, 2014 at 10:34:36AM +0200, Arnd Bergmann wrote:
>> commit e9ce7cb6b107 ("xen-netback: Factor queue-specific data into
>> queue struct") added a use of vzalloc/vfree to interface.c, but
>> removed the #include <linux/vmalloc.h> statement at the same time,
>> which causes this build error:
>>
>> drivers/net/xen-netback/interface.c: In function 'xenvif_free':
>> drivers/net/xen-netback/interface.c:754:2: error: implicit declaration of function 'vfree' [-Werror=implicit-function-declaration]
>> vfree(vif->queues);
>> ^
>> cc1: some warnings being treated as errors
>>
>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> Cc: Wei Liu <wei.liu2@citrix.com>
>> Cc: Andrew J. Bennieston <andrew.bennieston@citrix.com>
>
> Acked-by: Wei Liu <wei.liu2@citrix.com>
>
> This didn't happen to me when I built it on x86 though. Just curious,
> did you build it on othet platform, say, ARM?
ARM and PowerPC will both show this problem.
The issue is that x86 get's linux/vmalloc.h implicitly through one of
it's asm/ headers, thus you'll never hit the issue if you only build
test on that arch.
next prev parent reply other threads:[~2014-06-11 22:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 8:34 [PATCH] net: xen-netback: include linux/vmalloc.h again Arnd Bergmann
2014-06-10 8:44 ` Wei Liu
2014-06-10 8:52 ` [Xen-devel] " Ian Campbell
2014-06-11 22:19 ` David Miller [this message]
2014-06-12 9:07 ` Wei Liu
2014-06-11 22:19 ` David Miller
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=20140611.151901.986995853392690449.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew.bennieston@citrix.com \
--cc=arnd@arndb.de \
--cc=jwboyer@fedoraproject.org \
--cc=netdev@vger.kernel.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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).