From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, He Kuang <hekuang@huawei.com>,
lkml <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>,
David Ahern <dsahern@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] perf tools: Fix dwarf-aux.c compilation on i386
Date: Sat, 16 May 2015 08:21:49 +0200 [thread overview]
Message-ID: <20150516062149.GB12329@krava.redhat.com> (raw)
In-Reply-To: <20150515195931.GC17158@kernel.org>
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.
>
> Jiri,
>
> 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 ;-)
jirka
next prev parent reply other threads:[~2015-05-16 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 16:23 Jiri Olsa
2015-05-15 19:59 ` Arnaldo Carvalho de Melo
2015-05-16 6:21 ` Jiri Olsa [this message]
2015-05-18 1:20 ` Arnaldo Carvalho de Melo
2015-05-18 14:31 ` Jiri Olsa
2015-05-20 12:22 ` [tip:perf/core] " tip-bot for Jiri Olsa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150516062149.GB12329@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=dsahern@gmail.com \
--cc=hekuang@huawei.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome