From: Arnd Bergmann <email@example.com>
To: Deepa Dinamani <firstname.lastname@example.org>
Cc: Al Viro <email@example.com>,
Thomas Gleixner <firstname.lastname@example.org>,
Linux Kernel Mailing List <email@example.com>,
y2038 Mailman List <firstname.lastname@example.org>,
Linux FS-devel Mailing List <email@example.com>,
Linux API <firstname.lastname@example.org>,
Subject: Re: [PATCH 0/5] y2038: Make ppoll, io_pgetevents and pselect y2038 safe
Date: Fri, 14 Sep 2018 18:06:42 +0200 [thread overview]
Message-ID: <CAK8P3a3KLVEcCpPXWdEoOWgmP8zcDvLyj2LUn0Nw0+0yGO_MmA@mail.gmail.com> (raw)
On Sat, Sep 1, 2018 at 10:48 PM Deepa Dinamani <email@example.com> wrote:
> The series transitions the ppoll, io_getevents, and pselect syscalls
> to be y2038 safe.
> This is part of the work proceeding for syscalls for y2038.
> It is based on the series  from Arnd Bergmann.
> The overview of the series is as below:
> 1. Refactor sigmask handling logic for the above syscalls.
> 2. Provide y2038 safe versions of syscalls for all ABIs.
>  https://lkml.org/lkml/2018/8/27/651
This is a very nice series, sorry for taking way too long before
I had a good look at it.
The first two patches in particular are great. The third patch
looks like it has a small bug that I commented on, but given
how much more thought you have put into this than I did, it's
just as possible that I misunderstood it.
I've applied you series locally now, but have not pushed it out
yet for linux-next because of that one issue. I'll send a pull
request to Thomas for my other patches for now, and a
follow-up with these once we have clarified it.
prev parent reply other threads:[~2018-09-14 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 20:47 [PATCH 0/5] y2038: Make ppoll, io_pgetevents and pselect y2038 safe Deepa Dinamani
2018-09-01 20:47 ` [PATCH 1/5] signal: Add set_user_sigmask() Deepa Dinamani
2018-09-01 20:47 ` [PATCH 2/5] signal: Add restore_user_sigmask() Deepa Dinamani
2018-09-01 20:47 ` [PATCH 3/5] ppoll: use __kernel_timespec Deepa Dinamani
2018-09-14 15:57 ` Arnd Bergmann
2018-09-14 22:07 ` Deepa Dinamani
2018-09-01 20:47 ` [PATCH 4/5] pselect6: " Deepa Dinamani
2018-09-01 20:47 ` [PATCH 5/5] io_pgetevents: " Deepa Dinamani
2018-09-14 16:06 ` Arnd Bergmann [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).