From: David Miller <davem@davemloft.net>
To: sam@ravnborg.org
Cc: viro@ZenIV.linux.org.uk, rostedt@goodmis.org,
vapier.adi@gmail.com, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, akpm@linux-foundation.org,
mingo@elte.hu, tglx@linutronix.de
Subject: Re: [PATCH] make INIT_FS use the __RW_LOCK_UNLOCKED initialization
Date: Thu, 11 Dec 2008 20:28:07 -0800 (PST) [thread overview]
Message-ID: <20081211.202807.55399657.davem@davemloft.net> (raw)
In-Reply-To: <20081211212228.GB27223@uranus.ravnborg.org>
From: Sam Ravnborg <sam@ravnborg.org>
Date: Thu, 11 Dec 2008 22:22:28 +0100
> >
> > Guys, let's not take it to init/main.c, please. That file is basically
> > a trashcan and I'd rather take that stuff to more or less relevant places
> > in kernel/* and fs/*. FWIW, I've done that with init_files (fs/file.c)
> > some time ago. For init_fs... Hell knows. Might make sense to take
> > that to separate file, actually (kernel/exit.c and kernel/fork.c bits
> > related to fs_struct).
> >
> > BTW, why does sparc64 export put_fs_struct?
> I have sent a patch to davem now to get it removed.
It was used by the sunos and solaris syscall compat layers, which were
removed recently.
prev parent reply other threads:[~2008-12-12 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 23:37 [PATCH] make INIT_FS use the __RW_LOCK_UNLOCKED initialization Steven Rostedt
2008-12-10 23:43 ` Al Viro
2008-12-11 0:01 ` Steven Rostedt
2008-12-11 0:23 ` [PATCH] remove duplicate init_fs Steven Rostedt
2008-12-11 1:07 ` [PATCH] make INIT_FS use the __RW_LOCK_UNLOCKED initialization Mike Frysinger
2008-12-11 1:11 ` Steven Rostedt
2008-12-11 2:34 ` Al Viro
2008-12-11 21:22 ` Sam Ravnborg
2008-12-12 4:28 ` David Miller [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=20081211.202807.55399657.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
--cc=vapier.adi@gmail.com \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.