From: Li Zefan <lizf@cn.fujitsu.com>
To: jidong xiao <jidong.xiao@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where is proc_misc.c?
Date: Tue, 19 Jan 2010 14:56:39 +0800 [thread overview]
Message-ID: <4B5557A7.5000401@cn.fujitsu.com> (raw)
In-Reply-To: <4104961b1001182254x74f3fcd1r906de8f10c105f8a@mail.gmail.com>
jidong xiao wrote:
> Hi,
>
> Does anybody know what happend to fs/proc/proc_misc.c? The file is
> missing in 2.6.29. Seems like there was an cleanup, but i can't find
> the new location of the methods. Any help appreciated.
>
$ git log -- fs/proc/proc_misc.c
commit 59c7572e82d69483a66eaa67b46548baeb69ecf4
Author: Alexey Dobriyan <adobriyan@gmail.com>
Date: Mon Oct 6 14:49:39 2008 +0400
proc: remove fs/proc/proc_misc.c
Now that everything was moved to their more or less expected places,
apply rm(1).
Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
next prev parent reply other threads:[~2010-01-19 6:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-19 6:54 Where is proc_misc.c? jidong xiao
2010-01-19 6:56 ` Li Zefan [this message]
2010-01-19 7:34 ` jidong xiao
2010-01-19 14:34 ` Américo Wang
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=4B5557A7.5000401@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=jidong.xiao@gmail.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