From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id <S261836AbSJQTE2>; Thu, 17 Oct 2002 15:04:28 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org
	id <S261882AbSJQTE2>; Thu, 17 Oct 2002 15:04:28 -0400
Received: from nat-pool-rdu.redhat.com ([66.187.233.200]:46914 "EHLO
	devserv.devel.redhat.com") by vger.kernel.org with ESMTP
	id <S261836AbSJQTE1>; Thu, 17 Oct 2002 15:04:27 -0400
Date: Thu, 17 Oct 2002 15:10:21 -0400
From: Pete Zaitcev <zaitcev@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: Pete Zaitcev <zaitcev@redhat.com>
Subject: statfs64 status question
Message-ID: <20021017151021.A13386@devserv.devel.redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Guys,

can anyone remind me what is happening with the statfs64 syscall?
I can see that it is not in 2.5.

There was a little bit of discussion in May, but not much since then.

-- Pete