From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
y2038 Mailman List <y2038@lists.linaro.org>,
Chris Zankel <chris@zankel.net>,
fenghua.yu@intel.com, rth@twiddle.net,
Thomas Gleixner <tglx@linutronix.de>,
ubraun@linux.ibm.com, linux-alpha@vger.kernel.org,
linux-arch@vger.kernel.org, linux-ia64@vger.kernel.org,
"open list:RALINK MIPS ARCHITECTURE" <linux-mips@linux-mips.org>,
linux-s390 <linux-s390@vger.kernel.org>,
linux-xtensa@linux-xtensa.org,
sparclinux <sparclinux@vger.kernel.org>
Subject: Re: [PATCH v3 7/8] socket: Add SO_TIMESTAMPING_NEW
Date: Tue, 8 Jan 2019 08:40:18 -0500 [thread overview]
Message-ID: <CAF=yD-Jy7kyNtae7QpHgn6kJtmmYCngNdzF3K5DqVJBTHOUfqA@mail.gmail.com> (raw)
In-Reply-To: <20190108032657.8331-8-deepa.kernel@gmail.com>
On Mon, Jan 7, 2019 at 10:29 PM Deepa Dinamani <deepa.kernel@gmail.com> wrote:
>
> Add SO_TIMESTAMPING_NEW variant of socket timestamp options.
> This is the y2038 safe versions of the SO_TIMESTAMPING_OLD
> for all architectures.
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
> Cc: chris@zankel.net
> Cc: fenghua.yu@intel.com
> Cc: rth@twiddle.net
> Cc: tglx@linutronix.de
> Cc: ubraun@linux.ibm.com
> Cc: linux-alpha@vger.kernel.org
> Cc: linux-arch@vger.kernel.org
> Cc: linux-ia64@vger.kernel.org
> Cc: linux-mips@linux-mips.org
> Cc: linux-s390@vger.kernel.org
> Cc: linux-xtensa@linux-xtensa.org
> Cc: sparclinux@vger.kernel.org
> ---
> --- a/arch/sparc/include/uapi/asm/socket.h
> +++ b/arch/sparc/include/uapi/asm/socket.h
> @@ -106,20 +106,22 @@
> #define SO_TIMESTAMPNS_OLD 0x0021
> #define SO_TIMESTAMPING_OLD 0x0023
>
> -#define SO_TIMESTAMP_NEW 0x0040
> -#define SO_TIMESTAMPNS_NEW 0x0041
> +#define SO_TIMESTAMP_NEW 0x0041
> +#define SO_TIMESTAMPNS_NEW 0x0042
> +#define SO_TIMESTAMPING_NEW 0x0043
nit: unnecessary? perhaps need to get indentation consistent
immediately in the previous patch in this series that introduces
SO_TIMESTAMP_NEW
next prev parent reply other threads:[~2019-01-08 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 3:26 [PATCH v3 0/8] net: y2038-safe socket timestamps Deepa Dinamani
2019-01-08 3:26 ` [PATCH v3 1/8] arch: Use asm-generic/socket.h when possible Deepa Dinamani
2019-01-08 4:47 ` Max Filippov
2019-01-08 8:22 ` Heiko Carstens
2019-01-08 3:26 ` [PATCH v3 2/8] sockopt: Rename SO_TIMESTAMP* to SO_TIMESTAMP*_OLD Deepa Dinamani
2019-01-08 3:26 ` [PATCH v3 3/8] arch: sparc: Override struct __kernel_old_timeval Deepa Dinamani
2019-01-08 3:26 ` [PATCH v3 4/8] socket: Use old_timeval types for socket timestamps Deepa Dinamani
2019-01-08 3:26 ` [PATCH v3 5/8] socket: Add struct __kernel_sock_timeval Deepa Dinamani
2019-01-08 3:26 ` [PATCH v3 6/8] socket: Add SO_TIMESTAMP[NS]_NEW Deepa Dinamani
2019-01-08 13:46 ` Willem de Bruijn
2019-01-08 14:03 ` Willem de Bruijn
2019-01-08 3:26 ` [PATCH v3 7/8] socket: Add SO_TIMESTAMPING_NEW Deepa Dinamani
2019-01-08 13:40 ` Willem de Bruijn [this message]
2019-01-08 3:26 ` [PATCH v3 8/8] socket: Update timestamping Documentation Deepa Dinamani
2019-01-08 13:37 ` [PATCH v3 0/8] net: y2038-safe socket timestamps Willem de Bruijn
2019-01-08 13:53 ` Willem de Bruijn
2019-01-08 21:49 ` David Miller
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='CAF=yD-Jy7kyNtae7QpHgn6kJtmmYCngNdzF3K5DqVJBTHOUfqA@mail.gmail.com' \
--to=willemdebruijn.kernel@gmail.com \
--cc=arnd@arndb.de \
--cc=chris@zankel.net \
--cc=davem@davemloft.net \
--cc=deepa.kernel@gmail.com \
--cc=fenghua.yu@intel.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=netdev@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=sparclinux@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=ubraun@linux.ibm.com \
--cc=y2038@lists.linaro.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).