From: Keith Owens <kaos@sgi.com>
To: kdb@oss.sgi.com, linux-kernel@vger.kernel.org
Cc: linux-ia64@vger.kernel.org, sparclinux@vger.kernel.org
Subject: Announce: kdb v4.4 updates for for kernel 2.6.6
Date: Sun, 06 Jun 2004 10:04:14 +0000 [thread overview]
Message-ID: <12428.1086516254@ocs3.ocs.com.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
KDB (Linux Kernel Debugger) has been updated.
ftp://oss.sgi.com/projects/kdb/download/v4.4/
Current versions are :-
kdb-v4.4-2.6.6-common-2.bz2
kdb-v4.4-2.6.6-i386-2.bz2
kdb-v4.4-2.6.6-ia64-040521-2.bz2
kdb-v4.4-2.6.6-sparc64-1.bz2
Changelog extract since kdb-v4.3-2.6.6-common-2.
2004-06-06 Keith Owens <kaos@sgi.com>
* Avoid recursion problems in kdb_init().
* Add standard archkdb commands.
* Add per_cpu command.
* Move kdb_{get,put}userarea_size definitions to linux/kdb.h.
* kdb v4.4-2.6.6-common-2.
Changelog extract since kdb-v4.3-2.6.6-i386-1.
2004-06-06 Keith Owens <kaos@sgi.com>
* Correct Kconfig help text.
* Coexist with CONFIG_REGPARM.
* Add standard archkdb commands.
* Move kdb_{get,put}userarea_size definitions to linux/kdb.h.
* kdb v4.4-2.6.6-i386-2.
Changelog extract since kdb v4.3-2.6.6-rc3-ia64-1.
2004-06-06 Keith Owens <kaos@sgi.com>
* Add standard archkdb commands.
* Move kdb_{get,put}userarea_size definitions to linux/kdb.h.
* kdb v4.4-2.6.6-ia64-040521-2.
Changelog extract for sparc64.
2004-05-24 Tom Duffy <Thomas.Duffy.99@alumni.brown.edu>
* bump up to 2.6.6 kernel
* move to kdb 4.4 base
* kdb v4.4-2.6.6-sparc64-1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQFAwuwdi4UHNye0ZOoRAsJkAJ4iH0j6IaZsYZMEOabW4xMHw1wciACcCFey
ceeg7EBi97KqtgXUQe0Nw84=FvEk
-----END PGP SIGNATURE-----
reply other threads:[~2004-06-06 10:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=12428.1086516254@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=kdb@oss.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.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