2002-03-11 Tom Duffy <Thomas.Duffy.99@alumni.brown.edu>

	* backtracing will work right when we call kdb() directly.
	  Ethan Solomita <ethan@cs.columbia.edu>
	* kdb v2.1-2.4.18-sparc64-2

2002-02-26 Tom Duffy <Thomas.Duffy.99@alumni.brown.edu>

	* Upgrade to 2.4.18.
	* kdb v2.1-2.4.18-sparc64-1

2002-02-13 Tom Duffy <Thomas.Duffy.99@alumni.brown.edu>

	* valid_kernel_range now supports > 8byte ranges
	* kdb v2.1-2.4.17-sparc64-3

2002-02-02 Tom Duffy <Thomas.Duffy.99@alumni.brown.edu>

	* took suggested changes from kaos:
	* Call kdb(KDB_REASON_OOPS) directly from die_if_kernel
	* Call kdb after printing the oops, not before
	* Add a dummy kdba_prologue
	* Revert sparc64 changes to include/linux/kdbprivate.h and kdb/kdbsupport.c
	* kdb v2.1-2.4.17-sparc64-2

2002-02-01 Tom Duffy <Thomas.Duffy.99@alumni.brown.edu>

	* kdb v2.1-2.4.17-sparc64-1
