Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752768AbaJPOCB (ORCPT ); Thu, 16 Oct 2014 10:02:01 -0400 Received: from mail-yh0-f53.google.com ([209.85.213.53]:61064 "EHLO mail-yh0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751872AbaJPOCA (ORCPT ); Thu, 16 Oct 2014 10:02:00 -0400 MIME-Version: 1.0 In-Reply-To: <1413467180-32515-1-git-send-email-riku.voipio@linaro.org> References: <1413467180-32515-1-git-send-email-riku.voipio@linaro.org> Date: Thu, 16 Oct 2014 17:01:59 +0300 Message-ID: Subject: Re: [PATCH] gcov: add ARM64 to GCOV_PROFILE_ALL From: Riku Voipio To: Peter Oberparleiter , linux-kernel@vger.kernel.org Cc: "linux-arm-kernel@lists.infradead.org" , Andrew Morton , Stephen Rothwell , Riku Voipio Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 16 October 2014 16:46, Riku Voipio wrote: > Following up the arm testing of gcov, turns out gcov on ARM64 > works fine as well. Only change needed is adding ARM64 to Kconfig > depends. > > Tested with qemu and mach-virt > > Signed-off-by: Riku Voipio Sorry for the noise, this is the wrong patch. Will send the updated one a moment. Riku > --- > kernel/gcov/Kconfig | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/kernel/gcov/Kconfig b/kernel/gcov/Kconfig > index cf66c5c..3b74087 100644 > --- a/kernel/gcov/Kconfig > +++ b/kernel/gcov/Kconfig > @@ -35,7 +35,7 @@ config GCOV_KERNEL > config GCOV_PROFILE_ALL > bool "Profile entire Kernel" > depends on GCOV_KERNEL > - depends on SUPERH || S390 || X86 || PPC || MICROBLAZE || ARM > + depends on SUPERH || S390 || X86 || PPC || MICROBLAZE || ARM || ARM64 > default n > ---help--- > This options activates profiling for the entire kernel. > -- > 2.0.1 > -- 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/