From: Dave Jones <davej@codemonkey.org.uk>
To: Akira Tsukamoto <at541@columbia.edu>
Cc: Andrew Morton <akpm@digeo.com>,
linux-kernel@vger.kernel.org,
Hirokazu Takahashi <taka@valinux.co.jp>
Subject: Re: [PATCH] 2/2 2.5.45 cleanup & add original copy_ro/from_user
Date: Sun, 3 Nov 2002 21:24:21 +0000 [thread overview]
Message-ID: <20021103212421.GA733@suse.de> (raw)
In-Reply-To: <20021102214537.379A.AT541@columbia.edu>
On Sat, Nov 02, 2002 at 09:57:49PM -0500, Akira Tsukamoto wrote:
> Personally I don't mind adding everything in .h or .c.
> I just used the convention what string.h and string-486.h doing.
> Isn't it confusing that adding everything in .c also?
As a sidenote, string-486.h has been disabled for years
(Right back to at least 2.0.39 which is the earliest tree I have
to hand right now). It should either be fixed, or considered
worth dropping imo.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
next prev parent reply other threads:[~2002-11-03 21:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 8:06 [PATCH] 2/2 2.5.45 cleanup & add original copy_ro/from_user Akira Tsukamoto
2002-11-02 10:32 ` Andrew Morton
2002-11-02 11:07 ` Akira Tsukamoto
2002-11-02 18:13 ` Andrew Morton
2002-11-03 2:43 ` Akira Tsukamoto
2002-11-03 4:04 ` Andrew Morton
2002-11-03 2:43 ` Akira Tsukamoto
2002-11-03 2:57 ` Akira Tsukamoto
2002-11-03 21:24 ` Dave Jones [this message]
2002-11-03 22:22 ` Andries Brouwer
[not found] <20021102025838.220E.AT541@columbia.edu.suse.lists.linux.kernel>
[not found] ` <3DC3A9C0.7979C276@digeo.com.suse.lists.linux.kernel>
2002-11-02 10:58 ` Andi Kleen
2002-11-02 11:03 ` Andrew Morton
2002-11-02 16:55 ` Denis Vlasenko
2002-11-02 12:09 ` Andi Kleen
2002-11-02 17:08 ` Denis Vlasenko
2002-11-02 12:23 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2002-11-04 3:36 Akira Tsukamoto
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=20021103212421.GA733@suse.de \
--to=davej@codemonkey.org.uk \
--cc=akpm@digeo.com \
--cc=at541@columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=taka@valinux.co.jp \
/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.