From: "Kip Walker" <kwalker@broadcom.com>
To: "Juan Quintela" <quintela@mandrakesoft.com>
Cc: linux-mips@linux-mips.org, "Ralf Baechle" <ralf@linux-mips.org>
Subject: Re: [PATCH] add CONFIG_DEBUG_INFO
Date: Fri, 07 Mar 2003 07:27:50 -0800 [thread overview]
Message-ID: <3E68BA76.2A54D7CF@broadcom.com> (raw)
In-Reply-To: 86u1efp9rr.fsf@trasno.mitica
> I have no idea what the Corelis debugger is, but I assume that putting
> it configuration out of the CONFIG_KGDB is intentional? It doesn't
> require the -g option?
Yes -- the patch didn't include it, but the Corelis option will depend
on DEBUG_INFO. I just thought removing the nested ifdef was more
attractive, and have the configure magic deal with the dependence.
prev parent reply other threads:[~2003-03-07 15:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 19:34 [PATCH] rename CONFIG_REMOTE_DEBUG and CONFIG_DEBUG Jun Sun
2003-03-03 19:43 ` [PATCH] add CONFIG_DEBUG_INFO Kip Walker
2003-03-03 19:45 ` Kip Walker
2003-03-03 19:50 ` Juan Quintela
2003-03-06 16:47 ` Kip Walker
2003-03-07 13:48 ` Juan Quintela
2003-03-07 15:21 ` Ralf Baechle
2003-03-07 15:27 ` Kip Walker [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=3E68BA76.2A54D7CF@broadcom.com \
--to=kwalker@broadcom.com \
--cc=linux-mips@linux-mips.org \
--cc=quintela@mandrakesoft.com \
--cc=ralf@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