From: Andrew Morton <akpm@osdl.org>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: hch@infradead.org, rdreier@cisco.com, sam@ravnborg.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1 of 3] Introduce __raw_memcpy_toio32
Date: Tue, 10 Jan 2006 15:32:57 -0800 [thread overview]
Message-ID: <20060110153257.1aac5370.akpm@osdl.org> (raw)
In-Reply-To: <1136932162.6294.31.camel@serpentine.pathscale.com>
"Bryan O'Sullivan" <bos@pathscale.com> wrote:
>
> On Tue, 2006-01-10 at 14:05 -0800, Andrew Morton wrote:
>
> > It's kinda fun playing Brian along like this ;)
>
> A regular barrel of monkeys, indeed...
>
> > One option is to just stick the thing in an existing lib/ or kernel/ file
> > and mark it __attribute__((weak)). That way architectures can override it
> > for free with no ifdefs, no Makefile trickery, no Kconfig trickery, etc.
>
> I'm easy. Would you prefer to take that, or the Kconfig-trickery-based
> patch series I already posted earlier?
>
Unless someone can think of a problem with attribute(weak), I think you'll
find that it's the simplest-by-far solution.
next prev parent reply other threads:[~2006-01-10 23:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-06 20:26 [PATCH 0 of 3] 32-bit MMIO copy routine Bryan O'Sullivan
2006-01-06 20:26 ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Bryan O'Sullivan
2006-01-10 9:18 ` Andrew Morton
2006-01-10 14:55 ` Roland Dreier
2006-01-10 16:07 ` Bryan O'Sullivan
2006-01-10 16:56 ` [PATCH] [RFC] Generic 32-bit MMIO copy, out of line Bryan O'Sullivan
2006-01-10 17:07 ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Christoph Hellwig
2006-01-10 17:13 ` Bryan O'Sullivan
2006-01-10 17:49 ` Bryan O'Sullivan
2006-01-10 17:51 ` Christoph Hellwig
2006-01-10 17:55 ` Bryan O'Sullivan
2006-01-10 22:05 ` Andrew Morton
2006-01-10 22:29 ` Bryan O'Sullivan
2006-01-10 23:32 ` Andrew Morton [this message]
2006-01-11 17:20 ` Bryan O'Sullivan
2006-01-11 17:22 ` Sam Ravnborg
2006-01-11 17:30 ` Andrew Morton
2006-01-11 17:43 ` Bryan O'Sullivan
2006-01-11 18:49 ` Roland Dreier
2006-01-11 18:57 ` Bryan O'Sullivan
2006-01-11 19:01 ` Roland Dreier
2006-01-11 19:08 ` Bryan O'Sullivan
2006-01-13 15:19 ` Adrian Bunk
2006-01-10 18:02 ` Randy.Dunlap
2006-01-10 20:04 ` Sam Ravnborg
2006-01-10 15:59 ` Bryan O'Sullivan
2006-01-06 20:26 ` [PATCH 2 of 3] memcpy32 for x86_64 Bryan O'Sullivan
2006-01-06 20:26 ` [PATCH 3 of 3] Add __raw_memcpy_toio32 to each arch Bryan O'Sullivan
2006-01-10 19:53 [PATCH 0 of 3] 32-bit MMIO copy routines, reworked Bryan O'Sullivan
2006-01-10 19:53 ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Bryan O'Sullivan
2006-01-11 22:39 [PATCH 0 of 3] MMIO 32-bit copy routine, the final frontier Bryan O'Sullivan
2006-01-11 22:39 ` [PATCH 1 of 3] Introduce __raw_memcpy_toio32 Bryan O'Sullivan
2006-01-11 23:43 ` Andrew Morton
[not found] <5s6p8-1O3-29@gated-at.bofh.it>
[not found] ` <5s6p8-1O3-27@gated-at.bofh.it>
[not found] ` <5tnZx-1lb-17@gated-at.bofh.it>
[not found] ` <5tt8U-xV-5@gated-at.bofh.it>
[not found] ` <5tueu-2mb-9@gated-at.bofh.it>
[not found] ` <5tvaH-3MA-55@gated-at.bofh.it>
[not found] ` <5tvX6-4MO-13@gated-at.bofh.it>
[not found] ` <5tvX6-4MO-11@gated-at.bofh.it>
[not found] ` <5tvXa-4MO-23@gated-at.bofh.it>
[not found] ` <5tzQR-2zH-11@gated-at.bofh.it>
2006-01-15 15:33 ` Bodo Eggert
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=20060110153257.1aac5370.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=bos@pathscale.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=sam@ravnborg.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;
as well as URLs for NNTP newsgroup(s).