Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761174AbYGBJKS (ORCPT ); Wed, 2 Jul 2008 05:10:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753793AbYGBJKF (ORCPT ); Wed, 2 Jul 2008 05:10:05 -0400 Received: from an-out-0708.google.com ([209.85.132.240]:40801 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752910AbYGBJKD (ORCPT ); Wed, 2 Jul 2008 05:10:03 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=SaGxuOTKZlyZSkKle1//LG9iMod0pyhwzCm+0VDJiqweU7gxdtXRtPRNHiY39CGNna ilKyZV/JbnzyAwrgrnEz2+NdvcojKohR7XUGFbKwHaP7zkcJntE0o6Kuu2Z0UwDE+hUm SWKU5DVEUVMdO2ofFBoutM4CONT712pkYco9s= Message-ID: Date: Wed, 2 Jul 2008 13:10:02 +0400 From: "Alexander Beregalov" To: "Ingo Molnar" Subject: Re: next-0630: sparc64: build failed Cc: "Linux Kernel Mailing List" , linux-next@vger.kernel.org, sparclinux@vger.kernel.org, "David Miller" , sagar.abhishek@gmail.com, rostedt@goodmis.org In-Reply-To: <20080701154648.GA31057@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080701154648.GA31057@elte.hu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 668 Lines: 17 2008/7/1 Ingo Molnar : > thanks Alexander - does the patch below fix it for you? > commit 760378e1497841246ea7e42abad617d8a8ac0bcc > Author: Ingo Molnar > Date: Tue Jul 1 17:35:06 2008 +0200 > > fix "ftrace: store mcount address in rec->ip" > Yes, it fixes the issue. I have tried next-0702 which already includes your patch. But it has a name a1d5d08eb4f5c76acd5bb115e13791ce87ec356b. -- 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/