From: Arnd Bergmann <arnd@arndb.de>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linux FS-devel Mailing List <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
y2038 Mailman List <y2038@lists.linaro.org>
Subject: Re: [PATCH 1/2] select: Use get/put_timespec64
Date: Sat, 5 Aug 2017 21:53:49 +0200 [thread overview]
Message-ID: <CAK8P3a1bEQBAkum8Og=wSLKOdp5OnK_a74q3vxES8CpS=Qt8-Q@mail.gmail.com> (raw)
In-Reply-To: <20170805041232.20875-2-deepa.kernel@gmail.com>
On Sat, Aug 5, 2017 at 6:12 AM, Deepa Dinamani <deepa.kernel@gmail.com> wrote:
> Usage of these apis and their compat versions makes
> the syscalls: select family of syscalls and their
> compat implementations simpler.
>
> This is a preparatory patch to isolate data conversions to
> struct timespec64 at userspace boundaries. This helps contain
> the changes needed to transition to new y2038 safe types.
>
> Signed-off-by: Deepa Dinamani <deepa.kernel@gmail.com>
> ---
> fs/select.c | 60 ++++++++++++++++++++++++------------------------------------
> 1 file changed, 24 insertions(+), 36 deletions(-)
Looks all good to me,
Reviewed-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2017-08-05 19:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-05 4:12 [PATCH 0/2] i/o: Make i/o y2038 safe Deepa Dinamani
2017-08-05 4:12 ` [PATCH 1/2] select: Use get/put_timespec64 Deepa Dinamani
2017-08-05 19:53 ` Arnd Bergmann [this message]
2017-08-05 4:12 ` [PATCH 2/2] io_getevents: Use timespec64 to represent timeouts Deepa Dinamani
2017-08-05 20:13 ` Arnd Bergmann
2017-08-06 3:44 ` Deepa Dinamani
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='CAK8P3a1bEQBAkum8Og=wSLKOdp5OnK_a74q3vxES8CpS=Qt8-Q@mail.gmail.com' \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=deepa.kernel@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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).