Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754566AbYL0TPi (ORCPT ); Sat, 27 Dec 2008 14:15:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753509AbYL0TPa (ORCPT ); Sat, 27 Dec 2008 14:15:30 -0500 Received: from terminus.zytor.com ([198.137.202.10]:33066 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753394AbYL0TP3 (ORCPT ); Sat, 27 Dec 2008 14:15:29 -0500 Message-ID: <49567EB5.5030409@zytor.com> Date: Sat, 27 Dec 2008 11:15:01 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Sam Ravnborg CC: Ingo Molnar , Mike Frysinger , tglx@linutronix.de, mingo@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH] x86 byteorder.h: use __asm__/__inline__ for userspace References: <1230360604-6711-1-git-send-email-vapier@gentoo.org> <20081227071208.GB27736@uranus.ravnborg.org> <20081227084708.GA16077@elte.hu> <20081227185727.GB10442@uranus.ravnborg.org> <49567AC3.4030507@zytor.com> <20081227191223.GA10592@uranus.ravnborg.org> In-Reply-To: <20081227191223.GA10592@uranus.ravnborg.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1486 Lines: 36 Sam Ravnborg wrote: > On Sat, Dec 27, 2008 at 10:58:11AM -0800, H. Peter Anvin wrote: >> Sam Ravnborg wrote: >>> I wnet with the scripted conversion for now. >>> If that does not fly we can come back to this proposal. >>> >>> What I like most with the auto conversion is that we avoid >>> adding yet another special rule about how to do stuff in exported headers. >>> >> Indeed, and being keyword conversion, it's independent of context, at >> least as long as one doesn't have too many run-ins with weird uses of >> the # and ## preprocessor operators, which are a *lot* easier to rule >> out globally. > > Speaking of what we want to use in exported headers. > What is the recommendation with respect to uint32_t and friends? > To my best knowledge they are banned in exported headers as they > are not part of the kernel namespace and I see few users too. > But is this something we should check for? I personally would not be upset if we auto-changed {su}{8,16,32,64}, [u]int_{8,16,32,64}_t and bool into the appropriate __{su}{8,16,32,64} types and _Bool. I think the upside is way bigger than the potential downside. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- 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/