From: "David S. Miller" <davem@redhat.com>
To: Joshua Kwan <joshk@triplehelix.org>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix bug in sparc64 user copy patch
Date: Thu, 26 Aug 2004 17:06:39 -0700 [thread overview]
Message-ID: <20040826170639.130f54fd.davem@redhat.com> (raw)
In-Reply-To: <412E7730.4050309@triplehelix.org>
On Thu, 26 Aug 2004 16:50:08 -0700
Joshua Kwan <joshk@triplehelix.org> wrote:
> 1) clears the screen twice right after Remapping the kernel...
No idea.
> 2) omits every other character when it does start printing messages? such as
You're not following the list I guess... I even posted about
this to debian-sparc, ho hum.
There is a problem with sunsab serial consoles, we're still
trying to figure out exactly what. Note that console output
starts working properly once userland starts up.
next prev parent reply other threads:[~2004-08-27 0:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 22:52 [PATCH] fix bug in sparc64 user copy patch David S. Miller
2004-08-26 23:50 ` Joshua Kwan
2004-08-27 0:06 ` David S. Miller [this message]
2004-08-27 0:22 ` Joshua Kwan
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=20040826170639.130f54fd.davem@redhat.com \
--to=davem@redhat.com \
--cc=joshk@triplehelix.org \
--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