From: Ralph Mitchell <rmitchell@eds.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] SunSAB console problems in 2.6.x
Date: Sat, 28 Aug 2004 07:06:54 +0000 [thread overview]
Message-ID: <41302F0E.7060302@eds.com> (raw)
In-Reply-To: <20040825233247.237c1fb1.davem@redhat.com>
Works just fine. Thanks! Took me a minute to realise it was a patch
against 2.6.9-rc1, though. Are there any stability issues with this
RC? If not, I'll leave it running, otherwise I'll go back to 2.6.8.
Works even better with PREEMPT off. Thought I probably had something
stupid in the .config :)
Thanks,
Ralph Mitchell
David S. Miller wrote:
>On Fri, 27 Aug 2004 17:01:01 -0700
>Joshua Kwan <joshk@triplehelix.org> wrote:
>
>
>
>>>- mcount.o ipcsum.o rwsem.o xor.o splock.o find_bit.o
>>>+ mcount.o ipcsum.o rwsem.o xor.o splock.o find_bit.o delay.o
>>>
>>> lib-$(CONFIG_DEBUG_SPINLOCK) += debuglocks.o
>>> lib-$(CONFIG_HAVE_DEC_LOCK) += dec_and_lock.o
>>>
>>>
>>You forgot delay.c.
>>
>>
>
>Sorry, I'm a retard.
>
>This patch should be better.
>
># This is a BitKeeper generated diff -Nru style patch.
>#
># ChangeSet
># 2004/08/27 16:12:23-07:00 davem@nuts.davemloft.net
># [SPARC64]: Fix delay with HZ=1000.
>
>
prev parent reply other threads:[~2004-08-28 7:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 6:32 [PATCH] SunSAB console problems in 2.6.x David S. Miller
2004-08-26 8:31 ` Ralph Mitchell
2004-08-26 13:23 ` Ben Collins
2004-08-26 17:01 ` Ben Collins
2004-08-26 18:05 ` Ralph Mitchell
2004-08-26 20:19 ` David S. Miller
2004-08-27 0:43 ` Joshua Kwan
2004-08-27 1:10 ` David S. Miller
2004-08-27 10:30 ` Ralph Mitchell
2004-08-27 19:19 ` David S. Miller
2004-08-27 22:29 ` David S. Miller
2004-08-27 23:24 ` Joshua Kwan
2004-08-27 23:24 ` David S. Miller
2004-08-27 23:25 ` David S. Miller
2004-08-27 23:34 ` C.Newport
2004-08-27 23:39 ` David S. Miller
2004-08-28 0:01 ` Joshua Kwan
2004-08-28 0:04 ` David S. Miller
2004-08-28 7:06 ` Ralph Mitchell [this message]
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=41302F0E.7060302@eds.com \
--to=rmitchell@eds.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.