From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751998AbbERBUk (ORCPT ); Sun, 17 May 2015 21:20:40 -0400 Received: from mail.kernel.org ([198.145.29.136]:54557 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751375AbbERBUf (ORCPT ); Sun, 17 May 2015 21:20:35 -0400 Date: Sun, 17 May 2015 22:20:29 -0300 From: Arnaldo Carvalho de Melo To: Jiri Olsa Cc: Jiri Olsa , He Kuang , lkml , Peter Zijlstra , Paul Mackerras , David Ahern , Namhyung Kim , Ingo Molnar Subject: Re: [PATCH] perf tools: Fix dwarf-aux.c compilation on i386 Message-ID: <20150518012029.GA15972@kernel.org> References: <1431706991-15646-1-git-send-email-jolsa@kernel.org> <20150515195931.GC17158@kernel.org> <20150516062149.GB12329@krava.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150516062149.GB12329@krava.redhat.com> X-Url: http://acmel.wordpress.com User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Em Sat, May 16, 2015 at 08:21:49AM +0200, Jiri Olsa escreveu: > On Fri, May 15, 2015 at 04:59:31PM -0300, Arnaldo Carvalho de Melo wrote: > > Em Fri, May 15, 2015 at 06:23:11PM +0200, Jiri Olsa escreveu: > > > Replacing %lu format strings for Dwarf_Addr type with PRIu64 as it > > > fits for Dwarf_Addr (defined as uint64_t) type and works also on > > > both 32/64 bits. > > Please try to always indicate against which branch your patches > > should be applied, be it as [PATCH perf/core], [PATCH perf/urgent] for > > isolated patches, or on the cover letter [GIT PULL 0/N perf/core], or as > > I do with Ingo, "[GIT PULL] perf/core fixes". > > I thought, for this one, hey, its a fix, should go soon to Ingo! > > Tried to apply to perf/urgent, and it didn't apply :-\ > > Applying to perf/core instead now. > hum, I've never rebased against perf/urgent, I'll try > to squeeze it in next time ;-) In general, if it is a fix, try to check if it should be applied to perf/urgent first, if that is not the case, then it is fixing a bug introduced in perf/core, where it should go. If you don't make it clear where to apply, then the burden is on me to check, if I have to do it for everybody... it doesn't scale :-) - Arnaldo