Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Anirban Sinha <ASinha@zeugmasystems.com>
Cc: linux-mips@linux-mips.org
Subject: Re: kdb patches?!
Date: Fri, 22 Feb 2008 12:32:05 +0000	[thread overview]
Message-ID: <20080222123205.GC17312@linux-mips.org> (raw)
In-Reply-To: <DDFD17CC94A9BD49A82147DDF7D545C5842C91@exchange.ZeugmaSystems.local>

On Thu, Feb 21, 2008 at 01:08:26PM -0800, Anirban Sinha wrote:

> I know this has been previously discussed in the mailing list but since
> the last relevant post I see was Sept 2005, I ask again:
> 
> Has anyone done any work regarding porting kdb (*not* kgdb) patches to
> mips? Is there any recent (or hope of any future) work in this space? 

I've taken a stab at porting kdb in late 2004.  I still have the patches
sitting somewhere.  Various others seem tohave taken a stab at porting
kdn later on.

  Ralf

      parent reply	other threads:[~2008-02-22 12:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 21:08 kdb patches?! Anirban Sinha
2008-02-21 21:08 ` Anirban Sinha
2008-02-22 12:32 ` Ralf Baechle [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=20080222123205.GC17312@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=ASinha@zeugmasystems.com \
    --cc=linux-mips@linux-mips.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox