From: Andi Kleen <ak@suse.de>
To: Carlos O'Donell <carlos@baldric.uwo.ca>
Cc: willy@debian.org, akpm@osdl.org, linux-arch@vger.kernel.org
Subject: Re: compat-signal-noarch-2004-01-29.patch
Date: Sat, 28 Feb 2004 22:40:57 +0100 [thread overview]
Message-ID: <20040228224057.5959c8be.ak@suse.de> (raw)
In-Reply-To: <20040228202833.GB19963@baldric.uwo.ca>
On Sat, 28 Feb 2004 15:28:33 -0500
Carlos O'Donell <carlos@baldric.uwo.ca> wrote:
> > Is it really that hard to do the switch in architecture specific code?
>
> Yes, because I loathe the code duplication I'm seeing in all the arch
> directories. Please don't tell me that it's more maintainable that way.
It's about 5 lines of code. Not really a big issue. The bulk will be
shared.
> IMO, and I am not granted a crystal ball, the situation could be made
> cleaner through:
[...]
Not sure what this has to do with the issue at hand of adding an is_compat_task()
or not. I have no great opinion on fs/compat et.al vs arch/generic, filenames
really don't concern me.
-Andi
prev parent reply other threads:[~2004-02-28 21:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040225152204.2769a99b.akpm@osdl.org>
[not found] ` <20040226043605.GD17229@baldric.uwo.ca>
[not found] ` <20040229021045.78ac9466.ak@suse.de>
[not found] ` <20040226155930.GB24779@baldric.uwo.ca>
[not found] ` <20040226173115.7bd1aa86.ak@suse.de>
[not found] ` <20040226163812.GP25779@parcelfarce.linux.theplanet.co.uk>
[not found] ` <20040226174753.4319802c.ak@suse.de>
[not found] ` <20040226194747.GA28037@baldric.uwo.ca>
[not found] ` <20040226205058.5a0d1e34.ak@suse.de>
2004-02-27 23:40 ` compat-signal-noarch-2004-01-29.patch Carlos O'Donell
2004-03-02 20:39 ` compat-signal-noarch-2004-01-29.patch Andi Kleen
2004-02-28 19:15 ` compat-signal-noarch-2004-01-29.patch Carlos O'Donell
2004-02-28 19:36 ` compat-signal-noarch-2004-01-29.patch Andi Kleen
2004-02-28 20:28 ` compat-signal-noarch-2004-01-29.patch Carlos O'Donell
2004-02-28 21:40 ` Andi Kleen [this message]
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=20040228224057.5959c8be.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=carlos@baldric.uwo.ca \
--cc=linux-arch@vger.kernel.org \
--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