mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Hitoshi Mitake <h.mitake@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf tools: Fix an error on perf-bench document
Date: Thu, 28 Jun 2012 10:56:04 +0900	[thread overview]
Message-ID: <87395gyzbf.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <CAMO-S2j74+=9QJ40-=3Zj9a2M2wnCC474vsm216GP-BB9OWbsg@mail.gmail.com> (Hitoshi Mitake's message of "Wed, 27 Jun 2012 23:28:22 +0900")

On Wed, 27 Jun 2012 23:28:22 +0900, Hitoshi Mitake wrote:
> I wrote the simple fix for eliminatng wrong usage of "clock":
> https://github.com/mitake/linux/commit/b7836d41deff430c16058ca729120dccfa41e74e
>
> This patch assumes the change made by the Namhyung's patch. So I'm
> planning to send this after the Namhyung's patch is applied to tip
> tree. Or should the patches be unified before applied?

The patch is now in Arnaldo's tree. So you can see it in tip tree soon
unless something bad happens.

Anyway, looking at your commit (I think it's better just to send it via
email with mentioning the dependency), it seems only addresses memset
part but I think memcpy has the same problem, right?

Thanks,
Namhyung

  reply	other threads:[~2012-06-28  2:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-17 14:55 Namhyung Kim
2012-06-18  9:05 ` Ingo Molnar
2012-06-19  8:48   ` Namhyung Kim
2012-06-24 15:59     ` Hitoshi Mitake
2012-06-27 14:28       ` Hitoshi Mitake
2012-06-28  1:56         ` Namhyung Kim [this message]
2012-07-01 15:05           ` Hitoshi Mitake

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=87395gyzbf.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@ghostprotocols.net \
    --cc=h.mitake@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.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 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®