From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: [PATCH 1/3] bits/socket.h: Define SO_RCVBUFFORCE for mips
Date: Mon, 28 Apr 2014 10:29:35 -0400 [thread overview]
Message-ID: <20140428142935.GZ26358@brightrain.aerifal.cx> (raw)
In-Reply-To: <1398649434-23560-1-git-send-email-raj.khem@gmail.com>
On Sun, Apr 27, 2014 at 06:43:52PM -0700, Khem Raj wrote:
> packages like udev are using it
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>
> Upstream-Status: Pending
> ---
> arch/mips/bits/socket.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/mips/bits/socket.h b/arch/mips/bits/socket.h
> index ba79045..2264679 100644
> --- a/arch/mips/bits/socket.h
> +++ b/arch/mips/bits/socket.h
> @@ -31,6 +31,7 @@ struct cmsghdr
> #define SO_RCVBUF 0x1002
> #define SO_KEEPALIVE 8
> #define SO_OOBINLINE 256
> +#define SO_RCVBUFFORCE 33
>
> #define SO_NO_CHECK 11
> #define SO_PRIORITY 12
> --
> 1.7.10.4
I think this is correct, but are there additional new SO_*'s that
should be added to mips, or is this value the same as on other archs
and perhaps not something that should be arch-specific to begin with?
Rich
next prev parent reply other threads:[~2014-04-28 14:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 1:43 Khem Raj
2014-04-28 1:43 ` [PATCH 2/3] Add soname to dynamic section Khem Raj
2014-04-28 2:00 ` Rich Felker
2014-04-28 5:02 ` Khem Raj
2014-04-28 5:54 ` Isaac Dunham
2014-04-28 6:00 ` Khem Raj
2014-04-28 6:22 ` Isaac Dunham
2014-04-28 6:32 ` Timo Teras
2014-04-28 7:20 ` Khem Raj
2014-04-28 14:28 ` Rich Felker
2014-04-28 1:43 ` [PATCH 3/3] stddef: Define max_align_t Khem Raj
2014-04-28 2:03 ` Rich Felker
2014-04-28 5:51 ` Khem Raj
2014-04-28 10:11 ` Szabolcs Nagy
2014-04-28 12:22 ` Jens Gustedt
2014-04-28 13:26 ` Szabolcs Nagy
2014-04-28 13:59 ` Jens Gustedt
2014-04-28 14:14 ` Rich Felker
2014-04-28 14:29 ` Rich Felker [this message]
2014-04-28 14:54 ` [PATCH 1/3] bits/socket.h: Define SO_RCVBUFFORCE for mips Khem Raj
2014-04-30 18:48 ` Rich Felker
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=20140428142935.GZ26358@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).