From: Tom Rini <trini@kernel.crashing.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][1/6] A different KGDB stub
Date: Wed, 18 Feb 2004 13:23:57 -0700 [thread overview]
Message-ID: <20040218202357.GU16881@smtp.west.cox.net> (raw)
In-Reply-To: <20040218193624.GA408@elf.ucw.cz>
On Wed, Feb 18, 2004 at 08:36:24PM +0100, Pavel Machek wrote:
> Hi!
>
> > The following is the core bits to this KGDB stub.
>
> What are those weak functions good for? Can't we simply assume that
> any architecture that allows CONFIG_KGDB provides neccessary
> functions?
Not all arches need all functions, and that's where the weak functions
come in. We could remove some of them (the *gdb*regs* type ones) as
being absolutely required, but not everyone needs kgdb_arch_init.
Similarly for kgdb_flush_io.
> PS: Also.. how to proceed? Should I split your patches into "normal"
> and "lite" parts and submit to Amit?
Tomorrow I leave for FOSDEM, and won't have time to pick on KGDB until I
get back Tuesday. What I'm going to do then, if no one beats me to it,
is to merge stuff I've got into Amit's patches (the CVS versions off of
sourceforge), except for netpoll-specific portions of the kgdboe patch.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-02-18 20:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 22:02 Tom Rini
2004-02-17 23:50 ` Andrew Morton
2004-02-18 0:03 ` Tom Rini
2004-02-18 0:33 ` Andrew Morton
2004-02-18 0:39 ` Tom Rini
2004-02-25 17:50 ` Tom Rini
2004-02-18 19:36 ` Pavel Machek
2004-02-18 20:23 ` Tom Rini [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 0:02 Tom Rini
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=20040218202357.GU16881@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®