All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>
Cc: fweisbec@gmail.com, sparclinux@vger.kernel.org, tj@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] percpu misaligned allocation
Date: Thu, 18 Mar 2010 06:36:28 +0000	[thread overview]
Message-ID: <4BA1C9EC.2030801@cn.fujitsu.com> (raw)
In-Reply-To: <20100317.232834.115948373.davem@davemloft.net>

David Miller wrote:
> I can't even find kernel/trace/trace_event_perf.c, what tree

It's kernel/trace/trace_event_profile.c in linus' tree.

> are you using?

must be Ingo's -tip tree, or his own tree which is based on -tip tree.

WARNING: multiple messages have this Message-ID (diff)
From: Li Zefan <lizf@cn.fujitsu.com>
To: David Miller <davem@davemloft.net>
Cc: fweisbec@gmail.com, sparclinux@vger.kernel.org, tj@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG] percpu misaligned allocation
Date: Thu, 18 Mar 2010 14:36:28 +0800	[thread overview]
Message-ID: <4BA1C9EC.2030801@cn.fujitsu.com> (raw)
In-Reply-To: <20100317.232834.115948373.davem@davemloft.net>

David Miller wrote:
> I can't even find kernel/trace/trace_event_perf.c, what tree

It's kernel/trace/trace_event_profile.c in linus' tree.

> are you using?

must be Ingo's -tip tree, or his own tree which is based on -tip tree.

  reply	other threads:[~2010-03-18  6:36 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-18  4:49 [BUG] percpu misaligned allocation Frederic Weisbecker
2010-03-18  4:49 ` Frederic Weisbecker
2010-03-18  6:26 ` David Miller
2010-03-18  6:26   ` David Miller
2010-03-18  6:28   ` David Miller
2010-03-18  6:28     ` David Miller
2010-03-18  6:36     ` Li Zefan [this message]
2010-03-18  6:36       ` Li Zefan
2010-03-18  6:39   ` Li Zefan
2010-03-18  6:39     ` Li Zefan
2010-03-18 16:56     ` Frederic Weisbecker
2010-03-18 16:56       ` Frederic Weisbecker
2010-03-18  9:30 ` Tejun Heo
2010-03-18  9:30   ` Tejun Heo
2010-03-18 19:50   ` Frederic Weisbecker
2010-03-18 19:50     ` Frederic Weisbecker
2010-03-19  0:54   ` David Miller
2010-03-19  0:54     ` David Miller
2010-03-19  1:31     ` Frederic Weisbecker
2010-03-19  1:31       ` Frederic Weisbecker
2010-03-19  1:51       ` Tejun Heo
2010-03-19  1:51         ` Tejun Heo
2010-03-19  1:57       ` David Miller
2010-03-19  1:57         ` David Miller
2010-03-19  2:18         ` Tejun Heo
2010-03-19  2:18           ` Tejun Heo
2010-03-19  2:30           ` Frederic Weisbecker
2010-03-19  2:30             ` Frederic Weisbecker
2010-03-19  3:02           ` David Miller
2010-03-19  3:02             ` David Miller
2010-03-19 15:48             ` Richard Kennedy
2010-03-24 20:54 ` Maciej Rutecki

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=4BA1C9EC.2030801@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=davem@davemloft.net \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sparclinux@vger.kernel.org \
    --cc=tj@kernel.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 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.