Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754474AbZIXT3U (ORCPT ); Thu, 24 Sep 2009 15:29:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754387AbZIXT3S (ORCPT ); Thu, 24 Sep 2009 15:29:18 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:58050 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754414AbZIXT3P (ORCPT ); Thu, 24 Sep 2009 15:29:15 -0400 Date: Thu, 24 Sep 2009 21:29:13 +0200 From: Ingo Molnar To: John Kacur Cc: Peter Zijlstra , linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org, Fr??d??ric Weisbecker , Arnaldo Carvalho de Melo Subject: Re: [PATCH 0/3]Share common code between builtin-report, builtin-annotate Message-ID: <20090924192913.GA2533@elte.hu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) X-ELTE-SpamScore: -1.5 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-1.5 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.2.5 -1.5 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 796 Lines: 21 * John Kacur wrote: > builtin-annotate.c started out largely as a copy of builtin-report.c > In the meantime, fixes and enhancements have gone into builtin-report > but not always into builtin-annotate > > The goal here it to share code where possible. The first step is these > three patches - more work is comming. > > These three patches add util/sort.c and util/sort.h and move that > functionality out of builtin-report and builtin-annotate. Very nice patches! I've applied them to tip:perf/core, thanks John. Ingo -- 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/