From: Sebastian Gottschall <s.gottschall@dd-wrt.com>
To: musl@lists.openwall.com
Subject: SO_PEERSEC is wrong on MIPS / MIPS64 Systems
Date: Sun, 19 Aug 2018 20:11:13 +0200 [thread overview]
Message-ID: <efe4b93f-9268-cd0e-7513-db6248ca4899@dd-wrt.com> (raw)
In-Reply-To: <20180816235254.GL1878@brightrain.aerifal.cx>
musl defined SO_PEERSEC as 31, but on MIPS and MIPS64 systems it must be 30
and of course this isnt the only wrong one. see SO_SNDBUFFORCE 32 vs 31.
havent checked them all
Sebastian
next prev parent reply other threads:[~2018-08-19 18:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 18:11 Patches for gcc 8 Nagakamira
2018-08-16 23:52 ` Rich Felker
2018-08-17 6:30 ` Sebastian Gottschall
2018-08-17 8:48 ` Szabolcs Nagy
2018-08-19 18:11 ` Sebastian Gottschall [this message]
2018-08-19 18:19 ` SO_PEERSEC is wrong on MIPS / MIPS64 Systems Sebastian Gottschall
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=efe4b93f-9268-cd0e-7513-db6248ca4899@dd-wrt.com \
--to=s.gottschall@dd-wrt.com \
--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).