All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Hering <olh@suse.de>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	"Bryan O'Sullivan" <bos@pathscale.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Introduce __iowrite32_copy
Date: Thu, 2 Feb 2006 15:29:17 +0100	[thread overview]
Message-ID: <20060202142917.GA10870@suse.de> (raw)
In-Reply-To: <200602011820.k11IKUBo024575@hera.kernel.org>

 On Wed, Feb 01, Linux Kernel Mailing List wrote:

> tree c4d797b413bb6f8a1b8507213294a291ab5114f8
> parent f7589f28d7dd4586b4e90ac3b2a180409669053a
> author Bryan O'Sullivan <bos@pathscale.com> Wed, 01 Feb 2006 19:05:16 -0800
> committer Linus Torvalds <torvalds@g5.osdl.org> Thu, 02 Feb 2006 00:53:13 -0800
> 
> [PATCH] Introduce __iowrite32_copy
> 
> This arch-independent routine copies data to a memory-mapped I/O region,
> using 32-bit accesses.  The naming is double-underscored to make it clear
> that it does not guarantee write ordering, nor does it perform a memory
> barrier afterwards; the kernel doc also explicitly states this.  This style
> of access is required by some devices.
> 
> This change also introduces include/linux/io.h, at Andrew's suggestion.  It
> only has one occupant at the moment, but is a logical destination for
> oft-replicated contents of include/asm-*/{io,iomap}.h to migrate to.

> +++ b/lib/iomap_copy.c

> +void __attribute__((weak)) __iowrite32_copy(void __iomem *to,
> +					    const void *from,
> +					    size_t count)
> +{
> +	u32 __iomem *dst = to;
> +	const u32 *src = from;
> +	const u32 *end = src + count;
> +
> +	while (src < end)
> +		__raw_writel(*src++, dst++);
> +}

lib/iomap_copy.c: In function '__iowrite32_copy':
lib/iomap_copy.c:40: error: implicit declaration of function '__raw_writel'

We compile with -Werror-implicit-function-declaration, and s390 does not
have a __raw_writel.
Should it just define __raw_writel to writel, like uml does a few
commits later?

-- 
short story of a lazy sysadmin:
 alias appserv=wotan

       reply	other threads:[~2006-02-02 14:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200602011820.k11IKUBo024575@hera.kernel.org>
2006-02-02 14:29 ` Olaf Hering [this message]
2006-02-02 14:57   ` [PATCH] Introduce __iowrite32_copy Heiko Carstens
2006-02-02 16:49     ` Bryan O'Sullivan
2006-02-03  6:30     ` Al Viro
2006-02-03  8:34       ` Kars de Jong

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=20060202142917.GA10870@suse.de \
    --to=olh@suse.de \
    --cc=bos@pathscale.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    /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.