This message generated a parse failure. Raw output follows here. Please use 'back' to navigate. From devnull@lkml.org Mon May 6 12:53:24 2024 Received: from entropy.muc.muohio.edu (IDENT:root@entropy.muc.muohio.edu [134.53.213.10]) by herbie.ucs.indiana.edu (8.9.3/8.9.3) with ESMTP id FAA17170 for ; Fri, 9 Jul 1999 05:50:59 -0500 (EST) Received: from vger.rutgers.edu (vger.rutgers.edu [128.6.190.2]) by entropy.muc.muohio.edu (8.8.7/8.8.7) with ESMTP id GAA20475; Fri, 9 Jul 1999 06:45:23 -0400 Received: by vger.rutgers.edu via listexpand id ; Fri, 9 Jul 1999 06:41:21 -0400 Received: by vger.rutgers.edu id ; Fri, 9 Jul 1999 06:41:11 -0400 Received: from BC.Mountain.Net ([198.77.1.35]:3339 "EHLO bc.mountain.net") by vger.rutgers.edu with ESMTP id ; Fri, 9 Jul 1999 06:39:27 -0400 Received: from access2.mountain.net (root@Access2.mountain.net [198.77.1.71]) by bc.mountain.net (8.9.2/8.9.0) with ESMTP id GAA17666 for ; Fri, 9 Jul 1999 06:39:22 -0400 (EDT) Received: from access.mountain.net (AM11-1.Huntington-WV.Mountain.Net [198.77.57.100]) by access2.mountain.net (8.9.2/8.9.1) with ESMTP id GAA04841 for ; Fri, 9 Jul 1999 06:39:19 -0400 (EDT) Message-Id: <3785D04D.1D49DE07@access.mountain.net> Date: Fri, 09 Jul 1999 10:34:53 +0000 From: Tom Leete X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10 i486) X-Accept-Language: en-US,en-GB,en,fr,es,it,de,ru Mime-Version: 1.0 To: "linux-kernel@vger.rutgers.edu" Subject: [Fwd: Ansification: macros for all the rest] Content-Type: multipart/mixed; boundary="------------5F985E1DC3E01E38DF0BE580" Sender: owner-linux-kernel@vger.rutgers.edu Precedence: bulk X-Loop: majordomo@vger.rutgers.edu X-Orcpt: rfc822;linux-kernel-outgoing-dig This is a multi-part message in MIME format. --------------5F985E1DC3E01E38DF0BE580 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------5F985E1DC3E01E38DF0BE580 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3785D005.543AC7DB@access.mountain.net> Date: Fri, 09 Jul 1999 10:33:41 +0000 From: Tom Leete X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0; html=0; linewidth=0 X-Mailer: Mozilla 4.6 [en] (X11; I; Linux 2.2.10 i486) X-Accept-Language: en-US,en-GB,en,fr,es,it,de,ru MIME-Version: 1.0 To: Alan Cox Subject: Ansification: macros for all the rest Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, Here are the remaining patches for the substitution inline=>__inline__. I found no case where asm=>__asm__ was needed; the macro form is truly common practice in the headers. That's the stupid trivial mechanical part done. I wanted to do it separately and first, since I assumed it was uncontroversial. We'll see. From here on out I need to treat the headers individually, and I'll be dealing with their maintainers for that. No more bulk mail from me. I'm also posting the set at my homepage, sparing the kernel list further attachments. I'll send a copy of this to the list without attachments. If you please, I'd like to outline my plan for comment. The goal is to permit user-space developers to use gcc -pedantic or -ansi as a portability check on their code. This will have the side effect of permitting user-space developers to use their choice of tools. The next thing to go at is non-standard gcc extensions. Where these are needed by the kernel, I hope to be able to contain them in an #ifdef __KERNEL__ block. Where they are neutral or harmful to the kernel, I'll consult the maintainer about rewriting them. I'll save function macros for last. They will provide most of the hard cases. If they can't be isolated and can be improved by it, I'd like to change them to inline functions. Some of them may be technically impossible to change or isolate. That's ok, there's a -Wnowarn- for that and compilers agree on what they do. I'll consider the project a success if only these remain. In no case will I touch *.c files. This is strictly about prototypes for the exported symbols. Now I mean to go through the exported ksyms and test compile each corresponding header with gcc -pedantic. I'll get lots of warnings, and then I dig in. Regards, Tom "It is wise to resort to exclamations such as 'Help!' 'Hey!' etc."--J.T. --------------5F985E1DC3E01E38DF0BE580-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/