From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, akpm@osdl.org
Subject: Re: removing bcopy... because it's half broken
Date: Sun, 9 Jan 2005 20:03:01 +0000 [thread overview]
Message-ID: <20050109200301.B12788@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050109192305.GA7476@infradead.org>; from arjan@infradead.org on Sun, Jan 09, 2005 at 07:23:05PM +0000
On Sun, Jan 09, 2005 at 07:23:05PM +0000, Arjan van de Ven wrote:
> Nothing in the kernel is using bcopy right know, and that is a good thing.
> Why? Because a lot of the architectures implement a broken bcopy()....
> the userspace standard bcopy() is basically a memmove() with a weird
> parameter order, however a bunch of architectures implement a memcpy() not a
> memmove().
ARM doesn't implement bcopy() but does define __HAVE_ARCH_BCOPY - so
any users would error. Removing bcopy() is therefore no problem
afaics, and I'll lend my support by trying to will it to be gone. 8)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2005-01-09 20:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-09 19:23 removing bcopy... because it's half broken Arjan van de Ven
2005-01-09 19:39 ` Ralf Baechle
2005-01-09 20:03 ` Russell King [this message]
2005-01-09 20:19 ` Linus Torvalds
2005-01-09 20:33 ` Arjan van de Ven
2005-01-09 20:34 ` Christoph Hellwig
2005-01-09 20:42 ` Linus Torvalds
2005-01-11 10:10 ` Bastian Blank
2005-01-11 10:32 ` Arjan van de Ven
2005-01-11 16:10 ` Linus Torvalds
2005-01-09 23:38 ` Richard Henderson
2005-01-10 0:43 ` Adrian Bunk
2005-01-10 16:55 ` Matthias-Christian Ott
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=20050109200301.B12788@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.