From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@osdl.org>
Cc: lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/4] Trivial pgtable.h __ASSEMBLY__ move
Date: Thu, 03 Aug 2006 17:41:41 +1000 [thread overview]
Message-ID: <1154590902.11423.52.camel@localhost.localdomain> (raw)
[ Set of trivial cleanups taken from paravirt_ops work, please merge ]
Parsing generic pgtable.h in assembler is simply crazy. None of this file is
needed in assembler code, and C inline functions and structures routine break
one or more different compiles.
Signed-off-by: Zachary Amsden <zach@vmware.com>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal linux-2.6.18-rc2-mm1/include/asm-generic/pgtable.h working-2.6.18-rc2-mm1-zach-1/include/asm-generic/pgtable.h
--- linux-2.6.18-rc2-mm1/include/asm-generic/pgtable.h 2006-06-28 10:39:28.000000000 +1000
+++ working-2.6.18-rc2-mm1-zach-1/include/asm-generic/pgtable.h 2006-08-03 17:23:36.000000000 +1000
@@ -1,6 +1,8 @@
#ifndef _ASM_GENERIC_PGTABLE_H
#define _ASM_GENERIC_PGTABLE_H
+#ifndef __ASSEMBLY__
+
#ifndef __HAVE_ARCH_PTEP_ESTABLISH
/*
* Establish a new mapping:
@@ -188,7 +190,6 @@ static inline void ptep_set_wrprotect(st
})
#endif
-#ifndef __ASSEMBLY__
/*
* When walking page tables, we usually want to skip any p?d_none entries;
* and any p?d_bad entries - reporting the error before resetting to none.
--
Help! Save Australia from the worst of the DMCA: http://linux.org.au/law
next reply other threads:[~2006-08-03 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:41 Rusty Russell [this message]
2006-08-03 7:43 ` [PATCH 2/4] Trivial move of __HAVE macros in i386 pagetable headers Rusty Russell
2006-08-03 7:43 ` [PATCH 3/4] Trivial move of ptep_set_access_flags Rusty Russell
2006-08-03 7:44 ` [PATCH 4/4] Remove unused include from efi_stub.S Rusty Russell
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=1154590902.11423.52.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
Powered by JetHome