From: William Lee Irwin III <wli@holomorphy.com>
To: "Amit S. Kale" <amitkale@emsyssoft.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@suse.cz>,
Tom Rini <trini@kernel.crashing.org>,
George Anzinger <george@mvista.com>,
Steve Gonczi <steve@relicore.com>, Matt Mackall <mpm@selenic.com>
Subject: Re: kgdb 2.0.4 with restructuring and fixes
Date: Sat, 17 Jan 2004 02:01:27 -0800 [thread overview]
Message-ID: <20040117100127.GI1332@holomorphy.com> (raw)
In-Reply-To: <200401171451.38701.amitkale@emsyssoft.com>
On Sat, Jan 17, 2004 at 02:51:38PM +0530, Amit S. Kale wrote:
> kgdb 2.0.4 is available at http://kgdb.sourceforge.net ChangeLog below.
> Thanks.
> Amit Kale
> EmSysSoft (http://www.emsyssoft.com)
> KGDB: Linux Kernel Source Level Debugger (http://kgdb.sourceforge.net)
> 2004-01-17 Tom Rini <trini@kernel.crashing.org>
> * Some restructuring to allow architectures to provide different
> serial infos to the kgdb serial interface.
> 2004-01-17 Pavel Machek <pavel@suse.cz>
> * Cleanups
> * changed calling convention from 0 on success, 1 on failure to 0 on
> success, -ERRNO on fail to be more consistent with rest of kernel
> * Made kgdb waiting for connection message KERN_CRIT
> * export kern_schedule only if CONFIG_KGDB_THREAD is defined
This sound great. Any chance you could splatter this out at a patch
series to lkml for those of us so entrenched in pre-1994 conventions
(such as myself) as to dislike chasing URL's from mailing list posts?
-- wli
next prev parent reply other threads:[~2004-01-17 10:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 9:21 kgdb 2.0.4 with restructuring and fixes Amit S. Kale
2004-01-17 10:01 ` William Lee Irwin III [this message]
2004-01-17 10:24 ` Amit S. Kale
2004-01-17 10:51 ` William Lee Irwin III
2004-01-17 13:54 ` Pavel Machek
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=20040117100127.GI1332@holomorphy.com \
--to=wli@holomorphy.com \
--cc=amitkale@emsyssoft.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=pavel@suse.cz \
--cc=steve@relicore.com \
--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