From: Thomas Gleixner <tglx@linutronix.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: y2038 Mailman List <y2038@lists.linaro.org>,
Deepa Dinamani <deepa.kernel@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [tip GIT PULL] y2038: timekeeping syscall changes
Date: Thu, 19 Apr 2018 12:48:11 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1804191240510.1563@nanos.tec.linutronix.de> (raw)
In-Reply-To: <CAK8P3a2CEK=4Os4gbnXbR7VJJgaXVQ7NLjihr7rvMSK6g3_tNA@mail.gmail.com>
On Thu, 19 Apr 2018, Arnd Bergmann wrote:
> The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:
>
> Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)
>
> are available in the git repository at:
>
> git+ssh://gitolite@ra.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git
> tags/y2038-timekeeping
Please don't use the +ssh address as that's only accessible for those who
have a k.org account.
git://git.kernel.org/
is accessible for everyone.
> ----------------------------------------------------------------
> Arnd Bergmann (2):
> compat: add an asm-generic/compat.h file
Please start the subject line sentence with an uppercase letter.
> sparc: compat: allow including asm/compat.h for 32-bit
>
> Deepa Dinamani (10):
> compat: Make compat helpers independent of CONFIG_COMPAT
> include: Move compat_timespec/ timeval to compat_time.h
The proper subsystem is 'time:' not 'include:'
> compat: enable compat_get/put_timespec64 always
> arch: introduce CONFIG_64BIT_TIME
> arch: Introduce CONFIG_COMPAT_32BIT_TIME
At least it should be consistent..
> posix-clocks: Make compat syscalls depend on CONFIG_COMPAT_32BIT_TIME
'posix-timers:' please
> include: Add new y2038 safe __kernel_timespec
'time:'
> fix get_timespec64() for y2038 safe compat interfaces
Bah. This lacks a subsystem, i.e. 'time:'
> change time types to new y2038 safe __kernel_* types
Ditto
> nanosleep: change time types to safe __kernel_* types
Can you please fix that and send me an updated pull request?
Thanks,
tglx
next prev parent reply other threads:[~2018-04-19 10:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 9:35 [tip GIT PULL] y2038: timekeeping syscall changes Arnd Bergmann
2018-04-19 10:48 ` Thomas Gleixner [this message]
2018-04-19 12:04 ` Arnd Bergmann
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=alpine.DEB.2.21.1804191240510.1563@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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