From: "David S. Miller" <davem@redhat.com>
To: davidm@hpl.hp.com
Cc: davidm@napali.hpl.hp.com, arnd@arndb.de, ak@suse.de,
linux-arch@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH] fixing sendfile on 64bit architectures
Date: Wed, 19 May 2004 23:41:06 -0700 [thread overview]
Message-ID: <20040519234106.52b6db78.davem@redhat.com> (raw)
In-Reply-To: <16556.19979.951743.994128@napali.hpl.hp.com>
On Wed, 19 May 2004 23:19:55 -0700
David Mosberger <davidm@napali.hpl.hp.com> wrote:
> How about the attached? I decided to use __ARCH_OMIT_foo instead
> of SYS_NEED_foo since that keeps the extra code in those platforms
> that want to drop the code.
This looks OK to me.
next prev parent reply other threads:[~2004-05-20 6:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 19:26 [PATCH] fixing sendfile on 64bit architectures Arnd Bergmann
2004-05-20 6:19 ` David Mosberger
2004-05-20 6:41 ` David S. Miller [this message]
2004-05-23 9:37 ` Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 9:49 Andi Kleen
2004-05-19 12:21 ` Arnd Bergmann
2004-05-19 18:17 ` David Mosberger
2004-05-19 19:01 ` Andi Kleen
2004-05-19 19:13 ` David Mosberger
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=20040519234106.52b6db78.davem@redhat.com \
--to=davem@redhat.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arnd@arndb.de \
--cc=davidm@hpl.hp.com \
--cc=davidm@napali.hpl.hp.com \
--cc=linux-arch@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