From: Pavel Machek <pavel@ucw.cz>
To: Tom Rini <trini@kernel.crashing.org>
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 20:36:24 +0100 [thread overview]
Message-ID: <20040218193624.GA408@elf.ucw.cz> (raw)
In-Reply-To: <20040217220249.GB16881@smtp.west.cox.net>
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?
Pavel
PS: Also.. how to proceed? Should I split your patches into "normal"
and "lite" parts and submit to Amit?
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-02-18 19:37 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 [this message]
2004-02-18 20:23 ` Tom Rini
-- 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=20040218193624.GA408@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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
all inboxes | Powered by JetHome®