From: John Levon <movement@marcelothewonderpenguin.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sys_sysinfo overhaul
Date: Sat, 1 Jun 2002 01:17:23 +0100 [thread overview]
Message-ID: <20020601001723.GB91199@compsoc.man.ac.uk> (raw)
In-Reply-To: <1022879767.958.194.camel@sinai>
On Fri, May 31, 2002 at 02:16:07PM -0700, Robert Love wrote:
> - move sys_sysinfo to kernel/timer.c from kernel/info.c:
> why one small syscall got its own file is beyond me.
Huh ? What on earth is wrong with that ? Including a load of crap
in timer.c just increases false dependencies.
On the contrary, I wish the kernel had more file-level barriers.
john
prev parent reply other threads:[~2002-06-01 0:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-31 21:16 Robert Love
2002-06-01 0:17 ` John Levon [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=20020601001723.GB91199@compsoc.man.ac.uk \
--to=movement@marcelothewonderpenguin.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®