* Where is proc_misc.c?
@ 2010-01-19 6:54 jidong xiao
2010-01-19 6:56 ` Li Zefan
0 siblings, 1 reply; 4+ messages in thread
From: jidong xiao @ 2010-01-19 6:54 UTC (permalink / raw)
To: linux-kernel
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.
Regards
Jason
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Where is proc_misc.c?
2010-01-19 6:54 Where is proc_misc.c? jidong xiao
@ 2010-01-19 6:56 ` Li Zefan
2010-01-19 7:34 ` jidong xiao
0 siblings, 1 reply; 4+ messages in thread
From: Li Zefan @ 2010-01-19 6:56 UTC (permalink / raw)
To: jidong xiao; +Cc: linux-kernel
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>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Where is proc_misc.c?
2010-01-19 6:56 ` Li Zefan
@ 2010-01-19 7:34 ` jidong xiao
2010-01-19 14:34 ` Américo Wang
0 siblings, 1 reply; 4+ messages in thread
From: jidong xiao @ 2010-01-19 7:34 UTC (permalink / raw)
To: Li Zefan; +Cc: linux-kernel
On Tue, Jan 19, 2010 at 2:56 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
> 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>
>
>
Oh, I see. It looks like proc_misc.c has been splited into several
files, such as cmdline.c,version.c,uptime.c,meminfo.c.Thank you.
Regards
Jason
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Where is proc_misc.c?
2010-01-19 7:34 ` jidong xiao
@ 2010-01-19 14:34 ` Américo Wang
0 siblings, 0 replies; 4+ messages in thread
From: Américo Wang @ 2010-01-19 14:34 UTC (permalink / raw)
To: jidong xiao; +Cc: Li Zefan, linux-kernel
On Tue, Jan 19, 2010 at 03:34:31PM +0800, jidong xiao wrote:
>On Tue, Jan 19, 2010 at 2:56 PM, Li Zefan <lizf@cn.fujitsu.com> wrote:
>> 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>
>>
>>
>
>Oh, I see. It looks like proc_misc.c has been splited into several
>files, such as cmdline.c,version.c,uptime.c,meminfo.c.Thank you.
Or you can use:
git log --diff-filter=D fs/proc
--
Live like a child, think like the god.
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-01-19 14:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-01-19 6:54 Where is proc_misc.c? jidong xiao
2010-01-19 6:56 ` Li Zefan
2010-01-19 7:34 ` jidong xiao
2010-01-19 14:34 ` Américo Wang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox