From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: jason.wessel@windriver.com, linux-kernel@vger.kernel.org,
tglx@linutronix.de, hpa@zytor.com
Subject: Re: [PATCH] [KGDB] core code cleanups
Date: Sun, 27 Jan 2008 07:57:34 +0100 [thread overview]
Message-ID: <20080127065734.GA29514@elte.hu> (raw)
In-Reply-To: <20080126220106.4c1c2d5b.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> > thanks Jason, i have applied your cleanups to x86.git.
>
> I don't recall having actually seen the kgdb patches recently. Have
> they had a suitable level of review?
it was posted three months ago to lkml (the upteenth time) and we picked
it up into x86.git a month ago. KGDB has been problem-free in x86.git
ever since.
> In particular, as the plan is to migrate all kgdb-enabled
> architectures onto the generic kgdb core (yes?), have the owners of
> the eligible architectures actually taken a look at what we'll be
> asking of them?
at least as far as x86.git went the arch impact was refreshingly small.
There was some feedback that was addressed by Jason. (If any feedback is
still unaddressed then let us know - or if there are any new comments
i'm sure they will be addressed prompty - please keep the comments
coming!)
As more architectures enable support for KGDB, any specific objections
can and should be addressed on that level. (That's how we did it for
genirq and dynticks and that went far better than "address all
architecture concerns at once" - which delays merges forever. We'd still
be discussing irq flows versus flat irqs and clockevents versus drivers
if we did it like that.)
Ingo
prev parent reply other threads:[~2008-01-27 6:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 22:01 [PATCH] [KGDB] core code cleanups Jason Wessel
2008-01-25 22:28 ` Ingo Molnar
2008-01-27 6:01 ` Andrew Morton
2008-01-27 6:57 ` Ingo Molnar [this message]
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=20080127065734.GA29514@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--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