mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Luming Yu <luming.yu@gmail.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Christoph Hellwig <hch@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
	"Yu, Fenghua" <fenghua.yu@intel.com>,
	Felix Blyakher <felixb@sgi.com>,
	"Li, Shaohua" <shaohua.li@intel.com>,
	Bob Picco <bob.picco@hp.com>
Subject: Re: [RFC PATCH] Add TRACE_IRQFLAGS_SUPPORT, LOCKDEP_SUPPORT then  enable ftrace for ia64
Date: Sat, 5 Dec 2009 11:19:18 +0800	[thread overview]
Message-ID: <3877989d0912041919i458300d7ydce73cf77979dad3@mail.gmail.com> (raw)
In-Reply-To: <4BDB13256095B24D9644F65379E604265C12@orsmsx505.amr.corp.intel.com>

On Sat, Dec 5, 2009 at 3:16 AM, Luck, Tony <tony.luck@intel.com> wrote:
> Luming,
>
> Can you send the config file that you used to test this.

yes, will send my config later when back to office.

>
> I turned on a bunch of LOCKDEP related things, but I may have
> stumbled into areas that aren't working yet because my kernel
> didn't boot (or say anything on the console, even with early
> serial uart console enabled).

Please also send your config to me, let me check
what could make that happen.

>
> I'd like to take this patch so we can fix it up with incremental
> patches ... but I'd like a better idea of what works now and
> what doesn't.
>
> Thanks
>
> -Tony

Thanks.
Luming

  reply	other threads:[~2009-12-05  3:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  3:18 Luming Yu
2009-08-28  6:22 ` Ingo Molnar
2009-09-02 23:27   ` Luck, Tony
2009-09-03  8:46     ` Peter Zijlstra
2009-09-03 16:02       ` Luck, Tony
2009-12-04  7:29   ` Luming Yu
2009-12-04 19:16     ` Luck, Tony
2009-12-05  3:19       ` Luming Yu [this message]
2009-12-07  5:56         ` Luming Yu
2009-12-07 21:35           ` Tony Luck
2009-12-08 12:25             ` Luming Yu
2009-12-09  6:45               ` Luming Yu
2009-12-09  8:52                 ` Luming Yu
2009-12-09 18:11                   ` Tony Luck
2009-12-09 18:22                     ` Peter Zijlstra

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=3877989d0912041919i458300d7ydce73cf77979dad3@mail.gmail.com \
    --to=luming.yu@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=bob.picco@hp.com \
    --cc=felixb@sgi.com \
    --cc=fenghua.yu@intel.com \
    --cc=hch@infradead.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=shaohua.li@intel.com \
    --cc=tony.luck@intel.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®