From: Arnd Bergmann <arnd@arndb.de>
To: y2038@lists.linaro.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
Deepa Dinamani <deepa.kernel@gmail.com>,
linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk
Subject: Re: [Y2038] [PATCH 0/2] Add infrastructure to support vfs 64 bit timestamps
Date: Mon, 18 Apr 2016 00:39:20 +0200 [thread overview]
Message-ID: <6524641.PfjAxbWaQf@wuerfel> (raw)
In-Reply-To: <alpine.DEB.2.11.1604080848130.3860@nanos>
On Friday 08 April 2016 08:49:14 Thomas Gleixner wrote:
> On Fri, 8 Apr 2016, Deepa Dinamani wrote:
>
> > Resending for inclusion in Thomas's tree.
> >
> > The series contains infrastucture patches required to convert
> > vfs times to use 64 bit time.
> >
> > The intention is to include these as part of 4.6 so that the follow on
> > patches can go into 4.7.
> >
> > Patch 1 is as per the agreed upon RFC approach 2b:
> > https://lkml.org/lkml/2016/2/12/105
> > And, patch 2 is as per previously agreed upon discussion in:
> > https://lkml.org/lkml/2016/1/7/20
> >
> > The patches that will use these will be posted for the subsequent
> > kernel release.
>
> Al: Are you ok with those? Can you ship them to Linus or shall I route them?
It seems these fell through the cracks, any chance we can still get them
into 4.6?
Arnd
next prev parent reply other threads:[~2016-04-17 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-08 15:47 [PATCH 0/2] Add infrastructure to support vfs 64 bit timestamps Deepa Dinamani
2016-04-08 15:47 ` [PATCH 1/2] fs: Add current_fs_time_sec() function Deepa Dinamani
2016-04-09 1:16 ` Arnd Bergmann
2016-04-08 15:47 ` [PATCH 2/2] vfs: Add vfs_time accessors Deepa Dinamani
2016-04-09 1:17 ` Arnd Bergmann
2016-04-08 15:49 ` [PATCH 0/2] Add infrastructure to support vfs 64 bit timestamps Thomas Gleixner
2016-04-17 22:39 ` Arnd Bergmann [this message]
2016-04-26 16:15 ` 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=6524641.PfjAxbWaQf@wuerfel \
--to=arnd@arndb.de \
--cc=deepa.kernel@gmail.com \
--cc=linux-fsdevel@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