From: Andres Salomon <dilinger@mp3revolution.net>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.5.44-ac4
Date: Sun, 27 Oct 2002 16:29:50 -0500 [thread overview]
Message-ID: <20021027212950.GA15937@chunk.voxel.net> (raw)
In-Reply-To: <200210262357.g9QNvMP00380@devserv.devel.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2190 bytes --]
The following is necessary for sparc64 compilation.
On Sat, Oct 26, 2002 at 07:57:22PM -0400, Alan Cox wrote:
>
> ** I strongly recommend saying N to IDE TCQ options otherwise this
> should hopefully build and run happily.
>
> Most stuff is now back running at least as well as in 2.5.42-ac (u14f being
> the exception). This fixes a load more small things and resynchronizes the
> mmuless Linux stuff. That is now pretty close (IMHO) to mergable.
>
> Linux 2.5.44-ac4
> o Add 2.4.20-ac style /proc for ht info (Robert Love)
> o Fix bd_blocksize setting case (Hugh Dickins)
> o PCI bus setup now __devinit for hotplug (Ivan Kokshaysky)
> o make xconfig should work again (Alex Riesen)
> o Merge uclinux resync. This is now way cleaner (Christoph Hellwig)
> o Update znet driver (Marc Zyngier)
> o More i2o_scsi tidying (Christoph Hellwig)
> o Fix a leak in the device mapper (Joe Thornber)
> o Fix missed section name change (Peter Chubb)
> o Fix a bug in the APM update, add comments (me)
> o Merge block layer changes (Jens Axboe)
> | Should fix eject panic
> o Fix warnings in baycom_epp (me)
> o Fix warnings in fmvj18x, and timer_sync bug (me)
> o Fix sim710 warnings (me)
> o Fix pas16/t128 warnings (me)
> o Allow both mmio and pio g_NCR5380 builds at once(me)
> o Remove unused code from axnet_cs (me)
> o Fix warning in pc300 driver (me)
> o Clean up qlogicfas drivers somewhat (me)
> o Fix megaraid build for pci bios changes (me)
> o Fix cpu count weird reporting (Dave Jones)
> o Clean up capabilities printing (Dave Jones)
> o Silence mtrr debugging printk (Dave Jones)
> o Split machine check per processor (Dave Jones)
> o Update mpt fusion for new slave_attach handling (Peter Chubb)
> o Initial speedstep testing for VIA chipset boards(Bob Renwick)
>
> Linux 2.5.44-ac3
[...]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
It's not denial. I'm just selective about the reality I accept.
-- Bill Watterson
[-- Attachment #2: bug.h.diff --]
[-- Type: text/plain, Size: 237 bytes --]
--- a/include/asm-sparc64/bug.h 2002-10-27 13:02:47.000000000 -0500
+++ b/include/asm-sparc64/bug.h 2002-10-27 13:03:27.000000000 -0500
@@ -13,5 +13,6 @@
#define BUG() __builtin_trap()
#endif
+#define PAGE_BUG(page) BUG()
#endif
next prev parent reply other threads:[~2002-10-27 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-26 23:57 Alan Cox
2002-10-27 21:29 ` Andres Salomon [this message]
2002-10-27 1:20 Dieter Nützel
2002-10-27 2:58 Dieter Nützel
[not found] <200210270925.07460@advent.drealm.org.uk>
[not found] ` <200210271040.31765@advent.drealm.org.uk>
2002-10-27 11:52 ` Dave Jones
2002-10-27 12:11 ` Dave Jones
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=20021027212950.GA15937@chunk.voxel.net \
--to=dilinger@mp3revolution.net \
--cc=alan@redhat.com \
--cc=linux-kernel@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
Powered by JetHome