2.6.13.3-tiny1 for small systems

[Matt Mackall]

This is a resync of the -tiny tree against 2.6.13.3. The latest patch
can be found at:

 http://selenic.com/tiny/2.6.13.3-tiny1.patch.bz2
 http://selenic.com/tiny/2.6.13.3-tiny1-broken-out.tar.bz2

A Mercurial repository containing the latest broken out patches can be
found at:

 http://selenic.com/repo/tiny

There's a mailing list for linux-tiny development at:
 
 linux-tiny at selenic.com
 http://selenic.com/mailman/listinfo/linux-tiny

Webpage for your bookmarking pleasure:

 http://selenic.com/linux-tiny

Changes in this release:

+kbuild-fix-make-clean-damaging-hg-repos.patch

'make clean' damages Mercurial repositories by indiscriminately
deleting files starting with ".". Fixed in upstream.

-core-small.patch 
-pid-max.patch 
-user-hash.patch 
-futex-queues.patch 
-tvec_bases.patch 
-con_buf.patch 

Merged upstream

-06-crypto-sleep.patch 

No longer necessary

-kill-printk.patch 

Merged upstream

-nobug.patch 

Merged upstream

-no-kcore.patch 

Alternate version upstream

-semaphore-inline.patch 

Needs reworking

+kill-kmem_cache_name.patch

Fix a recent change that broke SLOB

-posix-timers.patch 

Needs reworking, may no longer be practical

-change-hz.patch 

Alternate version merged upstream

-inflate-killglobals.patch 
-inflate-initramfs.patch 
-inflate-initrd.patch 
-inflate-i386.patch 
-inflate-arm.patch 
-inflate-x86_64.patch 

This part of the inflate rework is refactored

+inflate-killmemzero.patch
+inflate-killdecls.patch
+inflate-killmarkrelease.patch
+inflate-makecrc.patch
+inflate-readbyte.patch
+inflate-flush.patch
+inflate-killsillytypes.patch
+inflate-error.patch
+inflate-tidyusers.patch
+inflate-killdebug.patch
+inflate-initdata.patch
+inflate-constdef.patch
+inflate-linkage.patch
+inflate-share-crc.patch

Extend the inflate changes to all architectures

-netpoll-timeout.patch 

Merged upstream

-- 
Mathematics is the supreme nostalgia of our time.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/