From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 8 Nov 2000 14:16:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 8 Nov 2000 14:16:17 -0500 Received: from 513.holly-springs.nc.us ([216.27.31.173]:54023 "EHLO 513.holly-springs.nc.us") by vger.kernel.org with ESMTP id ; Wed, 8 Nov 2000 14:16:11 -0500 Message-ID: <3A09A674.52B60BCD@holly-springs.nc.us> Date: Wed, 08 Nov 2000 14:16:04 -0500 From: Michael Rothwell X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.16 i686) X-Accept-Language: en MIME-Version: 1.0 To: Alan Cox , David Weinehall , linux-kernel@vger.kernel.org Subject: Re: Linux 2.2.18pre20 In-Reply-To: <3A08B759.1C36A9C0@holly-springs.nc.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hello? -M Michael Rothwell wrote: > > Alan Cox wrote: > > > > > On Tue, Nov 07, 2000 at 09:02:36PM -0500, Michael Rothwell wrote: > > > > 64-bit printk. > > > > > > Please consider this one Alan, if not for v2.2.18, then at least for > > > v2.2.19pre1. > > > > Nobody has explained why we even need it. > > Alan Cox wrote: > > > > Why do we need it ? > > To print 64-bit debugging output on 32-bit machines. I personally need > it to aid with development of a 64-bit filesystem. We're maintaining our > own 2.2.17 patched kernel here, but I figure that other people can make > use of 64-bit printk in their efforts as well. > > Perhaps a better question would be, why reject it? 2.4 supports 64-bit > printk, right? It would be nice to have it on 2.2 as well, as it may be > a while before 2.4 is widely used in production machines. > > -M - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/