From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org
Subject: 2.6.10-rc3-wli-1
Date: Wed, 22 Dec 2004 22:37:30 -0800 [thread overview]
Message-ID: <20041223063730.GY771@holomorphy.com> (raw)
Here it is. All sparc32 updates.
Most critical here are the HyperSPARC and sun4d updates as they get
things booting that weren't before, though neither fixes things all
the way. Another pretty nasty failure-to-boot issue that brings down
distro kernels is also resolved with Jurij Smakov's initrd memcpy() fix.
The main purpose of all this is so that sparc32 hackers and users can
see what's in and what isn't so they can complain about the fixes that
didn't get in and then I can include those when they remind me.
Available from:
ftp://ftp.kernel.org/pub/linux/kernel/people/wli/kernels/2.6.10-rc3/2.6.10-rc3-wli-1/2.6.10-rc3-wli-1.patch.bz2
+ linus.patch
sync with last night's bk
+ fix-hypersparc-dvma.patch
fix DVMA on UP HyperSPARC
+ newport-sun4d.patch
Christ Newport and Thomas Bogendoerfer's sun4d work
+ jurij-initrd-memcpy.patch
Jurij Smakov's memcpy() fixes
+ svr4-setcontext-return.patch
return something in an error path of svr4_setcontext()
+ pcic-warnings.patch
kill off some warnings in pcic.c
+ sunsu-warnings.patch
kill off some warnings in sunsu.c
+ rtc-warnings.patch
kill off some sparc RTC driver warnings
+ vm-fault-codes.patch
fix up VM fault code handling
+ spot-floppy-fix.patch
Tom Callaway's include/asm-sparc/floppy.h fixes
+ spot-exit-fix.patch
Tom Callaway's include/asm-sparc/unistd.h fixes
+ defconfig-update.patch
Tentative defconfig update. Bug wli if you want an option
turned on in the defconfig.
+ kropelin-breuer-cg6.patch
Adam Kropelin and Bob Breuer's cg6 fixes
-- wli
reply other threads:[~2004-12-23 6:37 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=20041223063730.GY771@holomorphy.com \
--to=wli@holomorphy.com \
--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