From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Randy Dunlap <rdunlap@xenotime.net>, dan.magenheimer@oracle.com
Cc: xen-devel@lists.xensource.com,
Stephen Rothwell <sfr@canb.auug.org.au>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for July 22 (xen)
Date: Fri, 22 Jul 2011 13:35:48 -0400 [thread overview]
Message-ID: <20110722173548.GA7698@dumpdata.com> (raw)
In-Reply-To: <20110722092245.589ec3d7.rdunlap@xenotime.net>
On Fri, Jul 22, 2011 at 09:22:45AM -0700, Randy Dunlap wrote:
> On Fri, 22 Jul 2011 16:42:37 +1000 Stephen Rothwell wrote:
>
> > Hi all,
Hey Randy,
This only shows up on xen but not xen-two?
>
> build errors & warnings: (full kernel config file is attached)
>
>
> drivers/xen/xen-selfballoon.c:95: warning: 'struct work_struct' declared inside parameter list
> drivers/xen/xen-selfballoon.c:95: warning: its scope is only this definition or declaration, which is probably not what you want
> drivers/xen/xen-selfballoon.c:96: warning: type defaults to 'int' in declaration of 'DECLARE_DELAYED_WORK'
> drivers/xen/xen-selfballoon.c:96: warning: parameter names (without types) in function declaration
> drivers/xen/xen-selfballoon.c:195: warning: 'struct work_struct' declared inside parameter list
> drivers/xen/xen-selfballoon.c:195: error: conflicting types for 'selfballoon_process'
> drivers/xen/xen-selfballoon.c:95: note: previous declaration of 'selfballoon_process' was here
> drivers/xen/xen-selfballoon.c: In function 'selfballoon_process':
> drivers/xen/xen-selfballoon.c:229: error: implicit declaration of function 'schedule_delayed_work'
> drivers/xen/xen-selfballoon.c:229: error: 'selfballoon_worker' undeclared (first use in this function)
> drivers/xen/xen-selfballoon.c:229: error: (Each undeclared identifier is reported only once
> drivers/xen/xen-selfballoon.c:229: error: for each function it appears in.)
> drivers/xen/xen-selfballoon.c:230: error: 'HZ' undeclared (first use in this function)
> drivers/xen/xen-selfballoon.c: In function 'store_selfballooning':
> drivers/xen/xen-selfballoon.c:266: error: 'selfballoon_worker' undeclared (first use in this function)
> drivers/xen/xen-selfballoon.c: In function 'xen_selfballoon_init':
> drivers/xen/xen-selfballoon.c:452: error: implicit declaration of function 'xen_domain'
> drivers/xen/xen-selfballoon.c:455: error: implicit declaration of function 'xen_initial_domain'
> drivers/xen/xen-selfballoon.c:478: error: 'selfballoon_worker' undeclared (first use in this function)
>
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-07-22 17:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 6:42 linux-next: Tree for July 22 Stephen Rothwell
2011-07-22 15:53 ` linux-next: Tree for July 22 (uml) Randy Dunlap
2011-07-22 16:04 ` linux-next: Tree for July 22 (bcma) Randy Dunlap
2011-07-22 16:22 ` linux-next: Tree for July 22 (xen) Randy Dunlap
2011-07-22 17:35 ` Konrad Rzeszutek Wilk [this message]
2011-07-22 17:48 ` Konrad Rzeszutek Wilk
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=20110722173548.GA7698@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=dan.magenheimer@oracle.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
--cc=xen-devel@lists.xensource.com \
/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).