From: Andrew Morton <akpm@linux-foundation.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Greg KH <greg@kroah.com>, Randy Dunlap <randy.dunlap@oracle.com>,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [patch 4/5] debugobjects: add timer specific object debugging code
Date: Sat, 26 Apr 2008 09:28:47 -0700 [thread overview]
Message-ID: <20080426092847.318a4fe0.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080321200321.731058197@linutronix.de>
On Fri, 21 Mar 2008 20:26:28 -0000 Thomas Gleixner <tglx@linutronix.de> wrote:
> Add calls to the generic object debugging infrastructure and provide
> fixup functions which allow to keep the system alive when recoverable
> problems have been detected by the object debugging core code.
>
This has run afoul of the new
http://ozlabs.org/~rusty/kernel/rr-latest/misc:timer-typesafe.patch
I don't know if Rusty intends that for 2.6.26. Probably not, given its
infancy. So I'll locally revert that change from Rusty's tree to clear the
way for a clean merge of
debugobjects-add-timer-specific-object-debugging-code.patch.
next prev parent reply other threads:[~2008-04-26 16:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 20:26 [patch 0/5] debugobject infrastructure V3 Thomas Gleixner
2008-03-21 20:26 ` [patch 1/5] slab: add a flag to prevent debug_free checks on a kmem_cache Thomas Gleixner
2008-03-21 20:26 ` [patch 2/5] infrastructure to debug (dynamic) objects Thomas Gleixner
2008-03-21 20:55 ` Randy Dunlap
2008-03-21 21:24 ` Thomas Gleixner
2008-03-24 20:04 ` Andrew Morton
2008-03-25 8:19 ` Thomas Gleixner
2008-03-26 23:23 ` Thomas Gleixner
2008-03-21 20:26 ` [patch 3/5] debugobjects: add documentation Thomas Gleixner
2008-03-21 20:26 ` [patch 4/5] debugobjects: add timer specific object debugging code Thomas Gleixner
2008-04-26 16:28 ` Andrew Morton [this message]
2008-03-21 20:26 ` [patch 5/5] add hrtimer specific debugobjects code Thomas Gleixner
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=20080426092847.318a4fe0.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=randy.dunlap@oracle.com \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
/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®