From: "David S. Miller" <davem@davemloft.net>
To: sparclinux@vger.kernel.org
Subject: Re: [4/3] fix initrd memcpy
Date: Tue, 21 Dec 2004 07:58:12 +0000 [thread overview]
Message-ID: <20041220235812.6ba77b91.davem@davemloft.net> (raw)
In-Reply-To: <20041221045627.GC771@holomorphy.com>
On Mon, 20 Dec 2004 23:00:25 -0800
William Lee Irwin III <wli@holomorphy.com> wrote:
> On Mon, Dec 20, 2004 at 10:39:01PM -0800, William Lee Irwin III wrote:
> > This looks tremendously cleaner. I'll look for an ack to see if there
> > are actively participating users lingering about with toolchains that
> > do something unintelligible out of paranoia and then send an analogue
> > of this upstream.
>
> tentative sparc32 analogue (not booted it yet):
Won't work, you have to fixup the memcpy.S code to return
the original destination pointer.
And you can't use the SETUP_RETL et al. stuff already there
since %g6 is used for the current thread pointer.
next prev parent reply other threads:[~2004-12-21 7:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-21 4:56 [4/3] fix initrd memcpy William Lee Irwin III
2004-12-21 6:28 ` David S. Miller
2004-12-21 6:39 ` William Lee Irwin III
2004-12-21 7:00 ` William Lee Irwin III
2004-12-21 7:58 ` David S. Miller [this message]
2004-12-21 8:28 ` William Lee Irwin III
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=20041220235812.6ba77b91.davem@davemloft.net \
--to=davem@davemloft.net \
--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.