All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Wang Nan <wangnan0@huawei.com>, Jiri Olsa <jolsa@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	lizefan@huawei.com, pi3orama@163.com
Subject: Re: [PATCH] perf: report: don't allow empty argument for '-t'.
Date: Thu, 19 Mar 2015 23:19:00 +0900	[thread overview]
Message-ID: <CAM9d7ciRVcg3aM=-DhvYpk2etO08Y_Kxcw3eVBm1HENUyP5F+w@mail.gmail.com> (raw)
In-Reply-To: <20150319140031.GH2983@kernel.org>

Hi Arnaldo,

On Thu, Mar 19, 2015 at 11:00 PM, Arnaldo Carvalho de Melo
<acme@kernel.org> wrote:
> Em Thu, Mar 19, 2015 at 04:26:24PM +0900, Namhyung Kim escreveu:
>> On Thu, Mar 19, 2015 at 02:41:42PM +0800, Wang Nan wrote:
>> > Hi Namhyung Kim,
>>
>> Hello,
>>
>> >
>> > Do you have any comment on it?
>>
>> As I said in previous reply, I think perf 'diff' and 'mem' have same
>> problem.  So how about fix them altogether?
>
> So you are ok with this change, right? Can I cound that as an ack? I.e.
> he could send the other fixes as separate patch(es).

I'm okay with it

Acked-by: Namhyung Kim <namhyung@kernel.org>

Thanks,
Namhyung

  reply	other threads:[~2015-03-19 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-13  8:41 [PATCH] perf: fix a segfault problem Wang Nan
2015-03-13  9:46 ` Namhyung Kim
2015-03-13 10:07   ` Wang Nan
2015-03-13 11:20     ` Namhyung Kim
2015-03-13 12:51       ` [PATCH] perf: report: don't allow empty argument for '-t' Wang Nan
2015-03-16  2:20         ` Namhyung Kim
2015-03-19  6:41         ` Wang Nan
2015-03-19  7:26           ` Namhyung Kim
2015-03-19 14:00             ` Arnaldo Carvalho de Melo
2015-03-19 14:19               ` Namhyung Kim [this message]
2015-03-22 10:13         ` [tip:perf/core] perf report: Don't " tip-bot for Wang Nan

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='CAM9d7ciRVcg3aM=-DhvYpk2etO08Y_Kxcw3eVBm1HENUyP5F+w@mail.gmail.com' \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizefan@huawei.com \
    --cc=mingo@redhat.com \
    --cc=pi3orama@163.com \
    --cc=wangnan0@huawei.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.