From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751359AbcARGKm (ORCPT ); Mon, 18 Jan 2016 01:10:42 -0500 Received: from mail-oi0-f68.google.com ([209.85.218.68]:35650 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750775AbcARGKj (ORCPT ); Mon, 18 Jan 2016 01:10:39 -0500 Date: Sun, 17 Jan 2016 22:09:26 -0800 From: Deepa Dinamani To: Andreas Dilger Cc: Arnd Bergmann , y2038@lists.linaro.org, Dave Chinner , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [Y2038] [RFC 02/15] vfs: Change all structures to support 64 bit time Message-ID: <20160118060925.GA15933@myubuntu.deepaubuntu.g7.internal.cloudapp.net> References: <1452144972-15802-1-git-send-email-deepa.kernel@gmail.com> <4756197.dta9JQvfZs@wuerfel> <6591497.mpSR1PpHzG@wuerfel> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Based on the discussion, here is how I propose to proceed: 1. Series for timestamp range check and clamping 2. Bug fixing patches like change all CURRENT_TIME use cases to current_fs_time() 3. Patches for vfs to use timespec64 internally (maybe a series, if required) 4. Patches that change all fs that use vfs APIs using timestamp arguments (not a series) 5. Change individual fs to use timespec64 (not a series) 6. Change back whatever time conversion APIs left in vfs or individual fs (maybe a series, if required) So, I don't see a need for submitting another series as all the changes now are handled on a case by case basis and no longer have a generic theme. If everyone's in sync then I can proceed with the above plan. -Deepa