linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Deepa Dinamani <deepa.kernel@gmail.com>
Cc: viro@zeniv.linux.org.uk, tglx@linutronix.de,
	linux-kernel@vger.kernel.org, y2038@lists.linaro.org,
	linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
	linux-aio@kvack.org
Subject: Re: [PATCH v4 0/5] y2038: Make ppoll, io_pgetevents and pselect y2038 safe
Date: Thu, 6 Dec 2018 17:26:54 +0100	[thread overview]
Message-ID: <CAK8P3a1d6KnCoGLY4tfkZzNVYBuWpHcov0se1ymtCGRMWOeTWw@mail.gmail.com> (raw)
In-Reply-To: <20180920044108.6606-1-deepa.kernel@gmail.com>

On 9/20/18, Deepa Dinamani <deepa.kernel@gmail.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 [1] 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 the syscalls for all ABIs.
>
> [1] https://lkml.org/lkml/2018/8/27/651

I'm sorry for dropping the ball on this earlier, so it already
missed the 4.20 merge window, and is getting almost too
late for 4.21 as well now.

I've applied your five patches to my y2038 tree now, so
it should at least be in linux-next as of tomorrow and
make it into 4.21. I'll see what other patches I have in
my backlog that we should get into that release before
I send him a pull request.

      Arnd

      parent reply	other threads:[~2018-12-06 16:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20  4:41 [PATCH v4 0/5] y2038: Make ppoll, io_pgetevents and pselect y2038 safe Deepa Dinamani
2018-09-20  4:41 ` [PATCH v4 1/5] signal: Add set_user_sigmask() Deepa Dinamani
2018-09-20  4:41 ` [PATCH v4 2/5] signal: Add restore_user_sigmask() Deepa Dinamani
2018-09-20  4:41 ` [PATCH v4 3/5] ppoll: use __kernel_timespec Deepa Dinamani
2018-09-20  4:41 ` [PATCH v4 4/5] pselect6: " Deepa Dinamani
2018-09-20  4:41 ` [PATCH v4 5/5] io_pgetevents: " Deepa Dinamani
2018-12-06 16:26 ` Arnd Bergmann [this message]

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=CAK8P3a1d6KnCoGLY4tfkZzNVYBuWpHcov0se1ymtCGRMWOeTWw@mail.gmail.com \
    --to=arnd@arndb.de \
    --cc=deepa.kernel@gmail.com \
    --cc=linux-aio@kvack.org \
    --cc=linux-api@vger.kernel.org \
    --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).