public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3.1-rc2] xen: self-balloon needs module.h
Date: Tue, 16 Aug 2011 01:11:22 -0400	[thread overview]
Message-ID: <20110816051122.GC27908@dumpdata.com> (raw)
In-Reply-To: <20110815214143.ed2fa458.rdunlap@xenotime.net>

On Mon, Aug 15, 2011 at 09:41:43PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@xenotime.net>
> 
> Fix build errors (found when CONFIG_SYSFS is not enabled):
> 
> drivers/xen/xen-selfballoon.c:446: warning: data definition has no type or storage class
> drivers/xen/xen-selfballoon.c:446: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL'
> drivers/xen/xen-selfballoon.c:446: warning: parameter names (without types) in function declaration
> drivers/xen/xen-selfballoon.c:485: error: expected declaration specifiers or '...' before string constant
> drivers/xen/xen-selfballoon.c:485: warning: data definition has no type or storage class
> drivers/xen/xen-selfballoon.c:485: warning: type defaults to 'int' in declaration of 'MODULE_LICENSE'
> drivers/xen/xen-selfballoon.c:485: warning: function declaration isn't a prototype
> 
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>

I think .. yeah I do have it queued it up in my stable/bug.fixes tree, .. ah
but did not push it (albeit it was in #linux-next which was pushed).

Linus, if you want to take it, it has my
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

or if you just want to do a git pull, I will shortly send an email asking
to pull the above mentioned tree.

> ---
>  drivers/xen/xen-selfballoon.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> and will need <linux/export.h> when module.h is split up.
> 
> --- lnx-31-rc2.orig/drivers/xen/xen-selfballoon.c
> +++ lnx-31-rc2/drivers/xen/xen-selfballoon.c
> @@ -70,6 +70,7 @@
>  #include <linux/kernel.h>
>  #include <linux/mm.h>
>  #include <linux/mman.h>
> +#include <linux/module.h>
>  #include <linux/workqueue.h>
>  #include <xen/balloon.h>
>  #include <xen/tmem.h>

      reply	other threads:[~2011-08-16  5:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-14 22:45 Linux 3.1-rc2 Linus Torvalds
2011-08-14 23:38 ` Linus Torvalds
2011-08-15  9:58 ` Paul Rolland
2011-08-15 17:18 ` [PATCH 3.1-rc2] x86: fix mm/fault.c build Randy Dunlap
2011-08-16  2:09   ` Linus Torvalds
2011-08-16  5:27     ` H. Peter Anvin
2011-08-16  6:00     ` Rule 1 (Was: Re: [PATCH 3.1-rc2] x86: fix mm/fault.c build) Stephen Rothwell
2011-08-16  6:20     ` [tip:x86/vdso] x86, vsyscall: Add missing <asm/fixmap.h> to arch/x86/mm/fault.c tip-bot for H. Peter Anvin
2011-08-16  6:43       ` Pekka Enberg
2011-08-16 15:02         ` H. Peter Anvin
2011-08-16 15:27     ` tip-bot for H. Peter Anvin
2011-08-16 17:23       ` Randy Dunlap
2011-08-16  4:41 ` [PATCH 3.1-rc2] xen: self-balloon needs module.h Randy Dunlap
2011-08-16  5:11   ` Konrad Rzeszutek Wilk [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=20110816051122.GC27908@dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=torvalds@linux-foundation.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