Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750839AbVJ3PWT (ORCPT ); Sun, 30 Oct 2005 10:22:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750952AbVJ3PWT (ORCPT ); Sun, 30 Oct 2005 10:22:19 -0500 Received: from palinux.external.hp.com ([192.25.206.14]:16049 "EHLO palinux.hppa") by vger.kernel.org with ESMTP id S1750839AbVJ3PWS (ORCPT ); Sun, 30 Oct 2005 10:22:18 -0500 Date: Sun, 30 Oct 2005 08:22:15 -0700 From: Matthew Wilcox To: Adrian Bunk Cc: grundler@parisc-linux.org, linux-kernel@vger.kernel.org, parisc-linux@parisc-linux.org Subject: Re: [parisc-linux] [2.6 patch] parisc: "extern inline" -> "static inline" Message-ID: <20051030152215.GB9235@parisc-linux.org> References: <20051030000301.GO4180@stusta.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051030000301.GO4180@stusta.de> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 754 Lines: 17 On Sun, Oct 30, 2005 at 02:03:01AM +0200, Adrian Bunk wrote: > "extern inline" doesn't make much sense. Are you sure? It used to. Taking just one sample, pgd_none: extern inline: alpha, parisc, s390 static inline: frv, ppc, sh64 define: arm, arm26, frv, h8300, m68knommu, ppc64, v850 I really don't think it makes any difference. Such a function (returning always 0) is always going to be inlined, and the only difference between static inline and extern inline is what happens when it can't be inlined. - 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/