Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1119320ybl; Fri, 30 Aug 2019 12:08:32 -0700 (PDT) X-Google-Smtp-Source: APXvYqzQdVFYnx7CAPrFAnTNRMyVwPkuwv6e/pYOcfEk/hC0gdsUYs5X001VC+FhfAYYZCS2n2tq X-Received: by 2002:a63:947:: with SMTP id 68mr14548016pgj.212.1567192112338; Fri, 30 Aug 2019 12:08:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567192112; cv=none; d=google.com; s=arc-20160816; b=ZfETXmAg4xQ7pcVuiQCPf0pdDJy2pq/TjTdcPFpp1L4d6U8IygmMaZ3XL4WMavZUJR jNca/XWljXxT3wazVTQPBgECshW9vOvOlaRhqKD6LuXPWT2GpWVpzRJr28psI0uSSm7P wgkL7Mys1tat9lDz0oIjsUtey2yeJwE74RzzbnOGl0XWElchSiL1dKR96TTU1GDwtd3X SHiDu1Xvw9F5iKtI9fQx4BfdQrSnxzwxndEkDWYCYp0SD9fTi7e0u9ixfKshPOCTCLdl gAY5Jfn4SM5N6ygEXBIDLQKkbsQyqM+AGiXEC6hXIly0Fp9eZFD0kySgParQYsMpGSpW LuGw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date; bh=oZQmb8nWpsXHjtedKFl5BO7xNOVGqwKohsD3tCxixx0=; b=HQAL0gsxrQoxWv0ykDJMy/6e+qMDcuJliJwlPRLn+RgI+Y9G1R1eNKnLF7b+RFGljc hgwkXZqYSq3oanOfwynTsRT0R+8RNxa6OV6QIycY5XT9w7KiTwWGS0JzCiY7VzKNKdOu hzNBjdUsLjtzji7tHeyOTqm2IyS795wFg/isPLk1USYWeUFKm6G+/HJryDokK5qnUG1+ hO/RYWG3w2ixBHuEfbfoGS0o5fNfoDOBRs96U3t5Zi1LcMLlDvlNEAs1AAq5QNi3il48 wNINAv7tPI4iGnl1ScVofGS2XWCHYpREj838noZVodWHubL/I+eGvCbE+Ic+0X9wpH0E 7BxA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s3si5045153pgq.392.2019.08.30.12.08.16; Fri, 30 Aug 2019 12:08:32 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728135AbfH3TGs (ORCPT + 99 others); Fri, 30 Aug 2019 15:06:48 -0400 Received: from mx2.suse.de ([195.135.220.15]:47312 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727891AbfH3TGr (ORCPT ); Fri, 30 Aug 2019 15:06:47 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 91770B01E; Fri, 30 Aug 2019 19:06:46 +0000 (UTC) Date: Fri, 30 Aug 2019 21:06:45 +0200 From: Michal =?UTF-8?B?U3VjaMOhbmVr?= To: linuxppc-dev@lists.ozlabs.org Cc: Benjamin Herrenschmidt , Paul Mackerras , Michael Ellerman , Christophe Leroy , Nicholas Piggin , Hari Bathini , Joel Stanley , Andrew Donnellan , Firoz Khan , Breno Leitao , Russell Currey , Nicolai Stange , Michael Neuling , "Eric W. Biederman" , Thomas Gleixner , Arnd Bergmann , Geert Uytterhoeven , Heiko Carstens , Christian Brauner , David Howells , Greg Kroah-Hartman , Allison Randal , David Hildenbrand , linux-kernel@vger.kernel.org Subject: Re: [PATCH v6 6/6] powerpc/perf: split callchain.c by bitness Message-ID: <20190830210645.78931423@kitsune.suse.cz> In-Reply-To: <567e7e876edf29ae528027d8574038fbc287f25a.1567188299.git.msuchanek@suse.de> References: <567e7e876edf29ae528027d8574038fbc287f25a.1567188299.git.msuchanek@suse.de> Organization: SUSE Linux X-Mailer: Claws Mail 3.17.1 (GTK+ 2.24.32; x86_64-suse-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 30 Aug 2019 20:57:57 +0200 Michal Suchanek wrote: > Building callchain.c with !COMPAT proved quite ugly with all the > defines. Splitting out the 32bit and 64bit parts looks better. > BTW the powerpc callchain.c does not match any of the patterns of PERF CORE in MAINTAINERS (unlike callchain implementation on other platforms). Is that intentional? Thanks Michal