From: Andrew Morton <akpm@osdl.org>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org,
"Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: [PATCH] bogus __KERNEL_SYSCALLS__ usage
Date: Thu, 12 Feb 2004 13:43:42 -0800 [thread overview]
Message-ID: <20040212134342.0874290a.akpm@osdl.org> (raw)
In-Reply-To: <20040212162856.GU12634@redhat.com>
Dave Jones <davej@redhat.com> wrote:
>
> I just did a mini-audit of users of __KERNEL_SYSCALLS and turned
> up a bunch of uglies. The patch below is the easy ones
OK. But Randy is currently beavering away at the astonishing number of
open-coded sys_foo() declarations, and that work has a significant
intersection with yours.
So can we please park this for now, pick it up again when Randy has
finished?
next prev parent reply other threads:[~2004-02-12 21:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 16:28 [PATCH] bogus __KERNEL_SYSCALLS__ usage Dave Jones
2004-02-12 19:31 ` Johannes Stezenbach
2004-02-12 21:43 ` Andrew Morton [this message]
2004-02-12 22:01 ` Dave Jones
2004-02-12 21:45 ` David Mosberger
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 22:16 Arnd Bergmann
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=20040212134342.0874290a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=torvalds@osdl.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