From: Randy Dunlap <[email protected]>
Update Documentation/s390/ files to reflect changed header files locations.
Signed-off-by: Randy Dunlap <[email protected]>
---
Documentation/s390/Debugging390.txt | 2 +-
Documentation/s390/cds.txt | 2 +-
Documentation/s390/s390dbf.txt | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
--- lin2628-rc3.orig/Documentation/s390/Debugging390.txt
+++ lin2628-rc3/Documentation/s390/Debugging390.txt
@@ -1402,7 +1402,7 @@ Syscalls are implemented on Linux for S3
possibilities of these as the instruction is made up of a 0xA opcode & the second byte being
the syscall number. They are traced using the simple command.
TR SVC <Optional value or range>
-the syscalls are defined in linux/include/asm-s390/unistd.h
+the syscalls are defined in linux/arch/s390/include/asm/unistd.h
e.g. to trace all file opens just do
TR SVC 5 ( as this is the syscall number of open )
--- lin2628-rc3.orig/Documentation/s390/cds.txt
+++ lin2628-rc3/Documentation/s390/cds.txt
@@ -98,7 +98,7 @@ platform. Some of the interface routines
of them can be found on other Linux platforms implementations too.
Miscellaneous function prototypes, data declarations, and macro definitions
can be found in the architecture specific C header file
-linux/include/asm-s390/irq.h.
+linux/arch/s390/include/asm/irq.h.
Overview of CDS interface concepts
--- lin2628-rc3.orig/Documentation/s390/s390dbf.txt
+++ lin2628-rc3/Documentation/s390/s390dbf.txt
@@ -2,7 +2,7 @@ S390 Debug Feature
==================
files: arch/s390/kernel/debug.c
- include/asm-s390/debug.h
+ arch/s390/include/asm/debug.h
Description:
------------