From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung.kim@lge.com>,
Namhyung Kim <namhyung@kernel.org>
Subject: Re: [PATCH v2 1/5] tools lib traceevent: Replace malloc_or_die to plain calloc in alloc_event()
Date: Mon, 18 Jun 2012 11:06:25 -0300 [thread overview]
Message-ID: <20120618140625.GH2303@infradead.org> (raw)
In-Reply-To: <1340027148.25903.90.camel@gandalf.stny.rr.com>
Em Mon, Jun 18, 2012 at 09:45:48AM -0400, Steven Rostedt escreveu:
> Arnaldo,
>
> I've acked this series. Can you add my Acked-by tags on the patches that
> do not have it yet, and then pull it into your repo?
Sure thing, I'll put it in my perf/core branch,
- Arnaldo
next prev parent reply other threads:[~2012-06-18 14:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 2:50 Namhyung Kim
2012-06-18 2:50 ` [PATCH v2 2/5] tools lib traceevent: Do not link broken field arg for an old ftrace event Namhyung Kim
2012-06-18 2:50 ` [PATCH v2 3/5] tools lib traceevent: Introduce pevent_errno Namhyung Kim
2012-06-18 2:50 ` [PATCH v2 4/5] tools lib traceevent: Introduce pevent_strerror Namhyung Kim
2012-06-18 13:41 ` Steven Rostedt
2012-06-18 2:50 ` [PATCH v2 5/5] scripts/tags.sh: Teach [ce]tags about libtraceeevent error codes Namhyung Kim
2012-06-18 13:44 ` Steven Rostedt
2012-07-26 12:24 ` Michal Marek
2012-06-18 13:37 ` [PATCH v2 1/5] tools lib traceevent: Replace malloc_or_die to plain calloc in alloc_event() Steven Rostedt
2012-06-18 13:45 ` Steven Rostedt
2012-06-18 14:06 ` Arnaldo Carvalho de Melo [this message]
2012-06-19 8:02 ` Namhyung Kim
2012-06-19 12:30 ` Steven Rostedt
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=20120618140625.GH2303@infradead.org \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®