[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1435781606-3037-1-git-send-email-jcboyd.dev@gmail.com>
Date: Wed, 1 Jul 2015 15:13:26 -0500
From: James C Boyd <jcboyd.dev@...il.com>
To: tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
corbet@....net, x86@...nel.org
Cc: linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
trivial@...nel.org
Subject: [PATCH] doc/x86/entry_64.txt: Use correct path names
The paths mentioned in this file weren't updated
through some file rename commits.
Fix them to refer to the correct path.
Signed-off-by: James C Boyd <jcboyd.dev@...il.com>
---
Documentation/x86/entry_64.txt | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/Documentation/x86/entry_64.txt b/Documentation/x86/entry_64.txt
index 33884d1..c1df8eb 100644
--- a/Documentation/x86/entry_64.txt
+++ b/Documentation/x86/entry_64.txt
@@ -1,14 +1,14 @@
This file documents some of the kernel entries in
-arch/x86/kernel/entry_64.S. A lot of this explanation is adapted from
+arch/x86/entry/entry_64.S. A lot of this explanation is adapted from
an email from Ingo Molnar:
http://lkml.kernel.org/r/<20110529191055.GC9835%40elte.hu>
The x86 architecture has quite a few different ways to jump into
kernel code. Most of these entry points are registered in
-arch/x86/kernel/traps.c and implemented in arch/x86/kernel/entry_64.S
-for 64-bit, arch/x86/kernel/entry_32.S for 32-bit and finally
-arch/x86/ia32/ia32entry.S which implements the 32-bit compatibility
+arch/x86/kernel/traps.c and implemented in arch/x86/entry/entry_64.S
+for 64-bit, arch/x86/entry/entry_32.S for 32-bit and finally
+arch/x86/entry/entry_64_compat.S which implements the 32-bit compatibility
syscall entry points and thus provides for 32-bit processes the
ability to execute syscalls when running on 64-bit kernels.
--
2.4.4
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists