Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
L
linux
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
linux
Commits
1941d9bc
Commit
1941d9bc
authored
Feb 06, 2004
by
Matthew Wilcox
Committed by
Linus Torvalds
Feb 06, 2004
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
[PATCH] PA-RISC needs IPC64 structs
PA-RISC also uses the 64-bit version of the IPC structs.
parent
0bd56a0a
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
2 additions
and
2 deletions
+2
-2
ipc/util.c
ipc/util.c
+1
-1
ipc/util.h
ipc/util.h
+1
-1
No files found.
ipc/util.c
View file @
1941d9bc
...
...
@@ -509,7 +509,7 @@ int ipc_checkid(struct ipc_ids* ids, struct kern_ipc_perm* ipcp, int uid)
return
0
;
}
#if !defined(__ia64__) && !defined(__x86_64__)
#if !defined(__ia64__) && !defined(__x86_64__)
&& !defined(__hppa__)
/**
* ipc_parse_version - IPC call version
...
...
ipc/util.h
View file @
1941d9bc
...
...
@@ -56,7 +56,7 @@ int ipc_checkid(struct ipc_ids* ids, struct kern_ipc_perm* ipcp, int uid);
void
kernel_to_ipc64_perm
(
struct
kern_ipc_perm
*
in
,
struct
ipc64_perm
*
out
);
void
ipc64_perm_to_ipc_perm
(
struct
ipc64_perm
*
in
,
struct
ipc_perm
*
out
);
#if defined(__ia64__) || defined(__x86_64__)
#if defined(__ia64__) || defined(__x86_64__)
|| defined(__hppa__)
/* On IA-64, we always use the "64-bit version" of the IPC structures. */
# define ipc_parse_version(cmd) IPC_64
#else
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment