From: Bobby Bingham <koorogi@koorogi.info>
To: musl@lists.openwall.com
Subject: [PATCH] remove or1k version of sem.h
Date: Tue, 5 Jul 2016 22:53:32 -0500 [thread overview]
Message-ID: <20160706035332.9987-1-koorogi@koorogi.info> (raw)
It's identical to the generic version, after evaluating the endian
preprocessor checks in the generic version.
---
arch/or1k/bits/sem.h | 11 -----------
1 file changed, 11 deletions(-)
delete mode 100644 arch/or1k/bits/sem.h
diff --git a/arch/or1k/bits/sem.h b/arch/or1k/bits/sem.h
deleted file mode 100644
index 0d91648..0000000
--- a/arch/or1k/bits/sem.h
+++ /dev/null
@@ -1,11 +0,0 @@
-struct semid_ds {
- struct ipc_perm sem_perm;
- time_t sem_otime;
- time_t __unused1;
- time_t sem_ctime;
- time_t __unused2;
- char __sem_nsems_pad[sizeof(time_t)-sizeof(short)];
- unsigned short sem_nsems;
- time_t __unused3;
- time_t __unused4;
-};
--
2.9.0
reply other threads:[~2016-07-06 3:53 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=20160706035332.9987-1-koorogi@koorogi.info \
--to=koorogi@koorogi.info \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).