Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759205AbXKLNiG (ORCPT ); Mon, 12 Nov 2007 08:38:06 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758364AbXKLNhy (ORCPT ); Mon, 12 Nov 2007 08:37:54 -0500 Received: from sovereign.computergmbh.de ([85.214.69.204]:59292 "EHLO sovereign.computergmbh.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758344AbXKLNhy (ORCPT ); Mon, 12 Nov 2007 08:37:54 -0500 Date: Mon, 12 Nov 2007 14:37:52 +0100 (CET) From: Jan Engelhardt To: Vegard Nossum cc: Andreas Schwab , "Robert P. J. Day" , axboe@kernel.dk, Linux Kernel Mailing List , Christoph Hellwig Subject: Re: [PATCH] Include header required for INT_MAX In-Reply-To: <19f34abd0711120457x720f0ac8q9d6d0632e6a970fb@mail.gmail.com> Message-ID: References: <19f34abd0711120457x720f0ac8q9d6d0632e6a970fb@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 861 Lines: 19 On Nov 12 2007 13:57, Vegard Nossum wrote: > >This seems like a good time to ask why the kernel doesn't use > for its INT_MAX and type definitions like uint32_t., etc. >>From the manpage: "The header is a subset of the > header more suitable for use in freestanding >environments, which might not support the formatted I/O functions. In >some environments, if the formatted conversion support is not >wanted, using this header instead of the header avoids >defining such a large number of macros." Yes, I am all for that, replacing u8 __u8 with uint8_t, and so on. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/