From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754050AbaBOVjh (ORCPT ); Sat, 15 Feb 2014 16:39:37 -0500 Received: from asav12.altibox.net ([81.167.36.146]:57848 "EHLO asav12.altibox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752965AbaBOVjf (ORCPT ); Sat, 15 Feb 2014 16:39:35 -0500 Date: Sat, 15 Feb 2014 22:28:27 +0100 From: Sam Ravnborg To: Andi Kleen Cc: linux-kernel@vger.kernel.org, x86@kernel.org, linux-kbuild@vger.kernel.org, mmarek@suse.cz, Andi Kleen Subject: Re: [PATCH 03/19] lto: Make asmlinkage __visible Message-ID: <20140215212827.GC27575@ravnborg.org> References: <1392412903-25733-1-git-send-email-andi@firstfloor.org> <1392412903-25733-4-git-send-email-andi@firstfloor.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1392412903-25733-4-git-send-email-andi@firstfloor.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 14, 2014 at 10:21:27PM +0100, Andi Kleen wrote: > From: Andi Kleen > > Note this causes warnings for static asmlinkage, which > is used in some places. These can be later cleaned up. > static asmlinkage usually makes no sense. > Reading the above changelog - it does not justify *why* asmlinkage is made visible. Sam