Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756014AbXLDVdT (ORCPT ); Tue, 4 Dec 2007 16:33:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752065AbXLDVdA (ORCPT ); Tue, 4 Dec 2007 16:33:00 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:33122 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751842AbXLDVdA (ORCPT ); Tue, 4 Dec 2007 16:33:00 -0500 Date: Tue, 4 Dec 2007 22:32:47 +0100 From: Ingo Molnar To: Harvey Harrison Cc: "H. Peter Anvin" , Thomas Gleixner , LKML Subject: Re: [RFC PATCH] x86: Unify include/asm-x86/linkage_[32|64].h Message-ID: <20071204213247.GA11216@elte.hu> References: <1196801629.10408.26.camel@brick> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1196801629.10408.26.camel@brick> User-Agent: Mutt/1.5.17 (2007-11-01) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.3 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 813 Lines: 21 * Harvey Harrison wrote: > I'm not sure if the definition of asmlinkage and prevent_tail_call can > be omitted as well and let the linux/linkage.h version get picked up > instead. no, we cannot remove them - asmlinkage is needed for the syscall entry (and other entry code) to work, the and the prevent_tail_call works around a compiler bug. (which might or might not be fixed in latest gcc - but we generally dont remove workarounds unless we are really sure it's fine.) so your patch looks good to me, i've queued it up. Ingo -- 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/