public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: jason.wessel@windriver.com, linux-kernel@vger.kernel.org,
	tglx@linutronix.de, hpa@zytor.com
Subject: Re: [PATCH] [KGDB] core code cleanups
Date: Sat, 26 Jan 2008 22:01:06 -0800	[thread overview]
Message-ID: <20080126220106.4c1c2d5b.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080125222836.GA24708@elte.hu>

> On Fri, 25 Jan 2008 23:28:36 +0100 Ingo Molnar <mingo@elte.hu> wrote:
> 
> * Jason Wessel <jason.wessel@windriver.com> wrote:
> 
> > This patch is against the x86-git which included the kgdb core.
> > 
> > Per review request from the x86-git maintainers, the kgdb-core has had 
> > the kgdb_handle_exception() separated into individual functions.  This 
> > patch does nothing other than re-organize the code.  There are no 
> > functional kgdb changes.
> > 
> > kgdb_handle_exception now calls gdb_serial_stub() to handle the 
> > debugger communications.  The gdb_serial_stub() has call out to sub 
> > handlers for all the major gdb serial packet types.
> 
> 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?

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?

  reply	other threads:[~2008-01-27  6:02 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 [this message]
2008-01-27  6:57     ` Ingo Molnar

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=20080126220106.4c1c2d5b.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jason.wessel@windriver.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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