From: Randy Dunlap <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: akpm <akpm@linux-foundation.org>,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: [PATCH 2/3] documentation: update s390 header file paths
Date: Tue, 04 Nov 2008 14:36:44 -0800 [thread overview]
Message-ID: <4910CE7C.2060709@xenotime.net> (raw)
From: Randy Dunlap <randy.dunlap@oracle.com>
Update Documentation/s390/ files to reflect changed header files locations.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
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:
------------
reply other threads:[~2008-11-04 22:50 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=4910CE7C.2060709@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
/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