public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin LaHaise <bcrl@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: [RFC][PATCH] cleanup file.h and INIT_TASK a bit
Date: Sun, 13 Jan 2002 18:59:47 -0500	[thread overview]
Message-ID: <20020113185947.A32700@redhat.com> (raw)

This patches does a couple of things: first off, it removes the sched.h 
include from file.h that was added recently, as we really don't need yet 
another include file chain mess.  To make this a bit more palatable, a 
few of the inlines are moved out of file.h and into fcntl.c, plus the 
files_struct is moved to file.h from sched.h.  Since this meant adding 
file.h to the various arch/*/kernel/init_task.c files, I took the time 
to move the INIT_* bits for initializing the init task out of sched.h 
and into init_task.h.  If this is okay, please apply the patch.  There 
are other cleanups to do if people are interested: the #define for init_task 
is currently duplicated in *all* asm-*/processor.h files to be exactly 
the same thing...  This is a way of testing the waters on include file 
cleanups.  Done properly, they shave ~10-15% off of the kernel compile 
time on my machine.

Oh, the file.h cleanup exposed a mess (bug): usb.c was duplicating code 
from daemonize().

		-ben
-- 
Fish.

             reply	other threads:[~2002-01-14  0:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-13 23:59 Benjamin LaHaise [this message]
     [not found] ` <3C4222C9.768F2C76@mandrakesoft.com>
2002-01-14  0:20   ` [RFC][PATCH] cleanup file.h and INIT_TASK a bit Benjamin LaHaise
2002-01-14  3:09 ` Greg KH
2002-01-15  4:35 ` Benjamin LaHaise
2002-01-15  4:50   ` Alexander Viro

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=20020113185947.A32700@redhat.com \
    --to=bcrl@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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