From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Deepa Dinamani <deepa.kernel@gmail.com>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Theodore Ts'o" <tytso@mit.edu>,
y2038@lists.linaro.org, Felipe Balbi <balbi@kernel.org>,
Steven Whitehouse <swhiteho@redhat.com>,
Ryusuke KONISHI <konishi.ryusuke@lab.ntt.co.jp>,
David Sterba <dsterba@suse.com>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH v5 0/5] Introduce current_time() api
Date: Tue, 27 Sep 2016 23:46:49 +0100 [thread overview]
Message-ID: <20160927224649.GM19539@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFx=A5nJgtxx9utSWzmmiDRuOwDXtVr0t_eg=9T6Z_ygPA@mail.gmail.com>
On Wed, Sep 14, 2016 at 09:45:55AM -0700, Linus Torvalds wrote:
> On Wed, Sep 14, 2016 at 7:48 AM, Deepa Dinamani <deepa.kernel@gmail.com> wrote:
> > The series is aimed at getting rid of CURRENT_TIME and CURRENT_TIME_SEC macros.
> > The macros are not y2038 safe. There is no plan to transition them into being
> > y2038 safe.
>
> This version looks ok to me.
>
> Al, would you be willing to queue this up for 4.9?
Applied.
prev parent reply other threads:[~2016-09-27 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 14:48 Deepa Dinamani
2016-09-14 14:48 ` [PATCH v5 1/5] vfs: Add " Deepa Dinamani
2016-09-14 18:52 ` Thomas Gleixner
2016-09-14 20:29 ` Deepa Dinamani
2016-09-14 20:33 ` Thomas Gleixner
2016-09-14 14:48 ` [PATCH v5 2/5] fs: proc: Delete inode time initializations in proc_alloc_inode() Deepa Dinamani
2016-09-14 14:48 ` [PATCH v5 3/5] fs: Replace CURRENT_TIME with current_time() for inode timestamps Deepa Dinamani
2016-09-14 14:48 ` [PATCH v5 4/5] fs: Replace CURRENT_TIME_SEC " Deepa Dinamani
2016-09-14 14:48 ` [PATCH v5 5/5] fs: Replace current_fs_time() with current_time() Deepa Dinamani
2016-09-14 16:45 ` [PATCH v5 0/5] Introduce current_time() api Linus Torvalds
2016-09-27 22:46 ` Al Viro [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=20160927224649.GM19539@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=balbi@kernel.org \
--cc=deepa.kernel@gmail.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=konishi.ryusuke@lab.ntt.co.jp \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swhiteho@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
--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
Powered by JetHome