From: Jes Sorensen <jes@sgi.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>, lguest <lguest@ozlabs.org>
Subject: [patch] lguest files should explicitly include asm/paravirt.h
Date: Thu, 09 Aug 2007 17:07:39 +0200 [thread overview]
Message-ID: <46BB2DBB.7050404@sgi.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 132 bytes --]
Hi,
This one makes a few lguest related files that rely on paravirt_ops
include paravirt.h explicitly. Should be harmless :)
Jes
[-- Attachment #2: paravirt-include.diff --]
[-- Type: text/plain, Size: 1189 bytes --]
Files using bits from paravirt.h should explicitly include it rather than
relying on it being pulled in by something else.
Signed-off-by: Jes Sorensen <jes@sgi.com>
---
drivers/char/hvc_lguest.c | 1 +
drivers/lguest/lguest_bus.c | 1 +
2 files changed, 2 insertions(+)
Index: linux-2.6-lguest/drivers/char/hvc_lguest.c
===================================================================
--- linux-2.6-lguest.orig/drivers/char/hvc_lguest.c
+++ linux-2.6-lguest/drivers/char/hvc_lguest.c
@@ -35,6 +35,7 @@
#include <linux/err.h>
#include <linux/init.h>
#include <linux/lguest_bus.h>
+#include <asm/paravirt.h>
#include "hvc_console.h"
/*D:340 This is our single console input buffer, with associated "struct
Index: linux-2.6-lguest/drivers/lguest/lguest_bus.c
===================================================================
--- linux-2.6-lguest.orig/drivers/lguest/lguest_bus.c
+++ linux-2.6-lguest/drivers/lguest/lguest_bus.c
@@ -5,6 +5,7 @@
#include <linux/bootmem.h>
#include <linux/lguest_bus.h>
#include <asm/io.h>
+#include <asm/paravirt.h>
static ssize_t type_show(struct device *_dev,
struct device_attribute *attr, char *buf)
reply other threads:[~2007-08-09 15:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46BB2DBB.7050404@sgi.com \
--to=jes@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=lguest@ozlabs.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.