From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754952AbaFBNwk (ORCPT ); Mon, 2 Jun 2014 09:52:40 -0400 Received: from relay1.mentorg.com ([192.94.38.131]:37627 "EHLO relay1.mentorg.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754438AbaFBNwf (ORCPT ); Mon, 2 Jun 2014 09:52:35 -0400 Date: Mon, 2 Jun 2014 13:52:19 +0000 From: "Joseph S. Myers" X-X-Sender: jsm28@digraph.polyomino.org.uk To: Arnd Bergmann CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , Subject: Re: [RFC 00/32] making inode time stamps y2038 ready In-Reply-To: <1401480116-1973111-1-git-send-email-arnd@arndb.de> Message-ID: References: <1401480116-1973111-1-git-send-email-arnd@arndb.de> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-OriginalArrivalTime: 02 Jun 2014 13:52:23.0625 (UTC) FILETIME=[E1752390:01CF7E69] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 30 May 2014, Arnd Bergmann wrote: > a) is this the right approach in general? The previous discussion > pointed this way, but there may be other opinions. The syscall changes seem like the sort of thing I'd expect, although patches adding new syscalls or otherwise affecting the kernel/userspace interface (as opposed to those relating to an individual filesystem) should go to linux-api as well as other relevant lists. -- Joseph S. Myers joseph@codesourcery.com