From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756019AbdCGToY (ORCPT ); Tue, 7 Mar 2017 14:44:24 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:47176 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755589AbdCGTnz (ORCPT ); Tue, 7 Mar 2017 14:43:55 -0500 Date: Tue, 7 Mar 2017 22:01:51 +0530 From: "Naveen N. Rao" To: Masami Hiramatsu Cc: Arnaldo Carvalho de Melo , Steven Rostedt , Ingo Molnar , linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Ananth N Mavinakayanahalli , Michael Ellerman Subject: Re: [PATCH 5/6] perf: probes: move ftrace README parsing logic into trace-event-parse.c References: <20170307165120.4e52fe447bd231d5e08a996f@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170307165120.4e52fe447bd231d5e08a996f@kernel.org> User-Agent: Mutt/1.6.2 (2016-07-01) X-TM-AS-MML: disable x-cbid: 17030716-0012-0000-0000-000003C689E5 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17030716-0013-0000-0000-00001B4BDDAA Message-Id: <20170307163151.GD11046@naverao1-tp.localdomain> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-03-07_11:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703070131 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2017/03/07 04:51PM, Masami Hiramatsu wrote: > On Tue, 7 Mar 2017 16:17:40 +0530 > "Naveen N. Rao" wrote: > > > probe-file.c needs libelf, but scanning ftrace README does not require > > that. As such, move the ftrace README scanning logic out of probe-file.c > > and into trace-event-parse.c. > > As far as I can see, there is no reason to push this out from probe-file.c > because anyway this API using code requires libelf. Without this, I can > still build perf with NO_LIBELF=1. So I wouldn't like to pick this. > (I think we can drop this from this series) Ok. We can drop this. I'll rework patch 6/6. Thanks, Naveen