From: Stephen Rothwell <sfr@canb.auug.org.au>
To: "David S. Miller" <davem@redhat.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
linux-kernel@vger.kernel.org, anton@samba.org, ak@muc.de,
davidm@hpl.hp.com, schwidefsky@de.ibm.com, ralf@gnu.org,
willy@debian.org
Subject: Re: [PATCH] Start of compat32.h (again)
Date: Mon, 2 Dec 2002 15:57:29 +1100 [thread overview]
Message-ID: <20021202155729.55949b10.sfr@canb.auug.org.au> (raw)
In-Reply-To: <1038804400.4411.4.camel@rth.ninka.net>
Hi Dave,
On 01 Dec 2002 20:46:40 -0800 "David S. Miller" <davem@redhat.com> wrote:
>
> On Sun, 2002-12-01 at 10:54, Linus Torvalds wrote:
> > But if the file is in kernel/xxxx, it
> > will be noticed - at least as well as it would be if it was uglifying
> > regular files with #ifdef's.
>
> Ok, this I accept.
So, does this mean you are happy if I produce patches with kernel/compat.c
in them rather than code #ifdef'ed into the mainline? This, of course,
begs the question of whether it should all go into kernel/compat.c or
should there be an fs/compat.c, mm/compat.c ...
At the moment, I just want to get something that we all agree on past
Linus and into his tree.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
next prev parent reply other threads:[~2002-12-02 4:51 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 7:42 Stephen Rothwell
2002-11-27 7:58 ` David S. Miller
2002-11-27 13:00 ` Stephen Rothwell
2002-11-28 5:27 ` David S. Miller
2002-11-27 18:51 ` Linus Torvalds
2002-11-28 5:34 ` David S. Miller
2002-11-27 8:00 ` David Mosberger
2002-11-27 8:06 ` David S. Miller
2002-11-27 8:29 ` Andi Kleen
2002-11-27 8:46 ` David Mosberger
2002-11-27 9:01 ` Andi Kleen
2002-11-27 9:57 ` David S. Miller
2002-11-27 17:10 ` David Mosberger
2002-11-28 5:29 ` David S. Miller
2002-11-27 12:49 ` Alan Cox
2002-11-30 20:34 ` Ralf Baechle
2002-11-27 17:18 ` Linus Torvalds
2002-11-28 5:22 ` Stephen Rothwell
2002-11-28 5:26 ` David S. Miller
2002-11-29 2:36 ` Stephen Rothwell
2002-12-01 18:54 ` Linus Torvalds
2002-12-02 4:46 ` David S. Miller
2002-12-02 4:57 ` Stephen Rothwell [this message]
2002-12-02 6:17 ` David S. Miller
2002-12-02 7:39 ` Richard Henderson
2002-12-02 7:44 ` David S. Miller
2002-12-02 7:59 ` Ralf Baechle
2002-12-02 8:01 ` David S. Miller
2002-12-04 11:22 ` Pavel Machek
2002-12-05 21:04 ` David S. Miller
2002-11-28 5:31 ` David S. Miller
2002-11-29 4:45 ` [PATCH] 32 bit consolidation 1/Many (was: [PATCH] Start of compat32.h (again)) Stephen Rothwell
2002-11-29 4:52 ` [PATCH] 32 bit consolidation 2/Many Stephen Rothwell
[not found] <Pine.LNX.4.44.0212011047440.12964-100000@home.transmeta.com.suse.lists.linux.kernel>
[not found] ` <1038804400.4411.4.camel@rth.ninka.net.suse.lists.linux.kernel>
2002-12-02 8:13 ` [PATCH] Start of compat32.h (again) Andi Kleen
2002-12-02 8:28 ` David S. Miller
2002-12-02 9:07 ` Andi Kleen
2002-12-02 9:36 ` Jakub Jelinek
2002-12-02 17:01 ` Mikael Pettersson
2002-12-02 10:16 ` David S. Miller
2002-12-04 11:19 ` Pavel Machek
2002-12-05 21:06 ` David S. Miller
2002-12-05 21:21 ` Pavel Machek
2002-12-05 21:22 ` David S. Miller
2002-12-05 21:32 ` Pavel Machek
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=20021202155729.55949b10.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ak@muc.de \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@gnu.org \
--cc=schwidefsky@de.ibm.com \
--cc=torvalds@transmeta.com \
--cc=willy@debian.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
all inboxes | Powered by JetHome®