From: Andreas Schwab <schwab@linux-m68k.org>
To: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
Cc: "linuxppc-dev\@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: ppc32: semctl fails
Date: Wed, 06 Dec 2017 23:56:06 +0100 [thread overview]
Message-ID: <87lgif31q1.fsf@linux-m68k.org> (raw)
In-Reply-To: <1512581010.8313.153.camel__41464.7176782184$1512581316$gmane$org@infinera.com> (Joakim Tjernlund's message of "Wed, 6 Dec 2017 17:23:33 +0000")
On Dez 06 2017, Joakim Tjernlund <Joakim.Tjernlund@infinera.com> wrote:
> st = semctl(sem, 0, IPC_STAT, &arg);
This is not a valid use of IPC_STAT. The fourth argument must be a
object of type union semun (not a pointer), with the .buf member
pointing to the struct semid_ds object.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next parent reply other threads:[~2017-12-06 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1512581010.8313.153.camel__41464.7176782184$1512581316$gmane$org@infinera.com>
2017-12-06 22:56 ` Andreas Schwab [this message]
2017-12-06 23:53 ` ppc32: semctl fails Joakim Tjernlund
2017-12-06 17:23 Joakim Tjernlund
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=87lgif31q1.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=Joakim.Tjernlund@infinera.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).