> Agreed. However the direction I am gradually moving fs/proc/base.c
> is the opposite.
Oh - ok fine.
I had seen something from Andrew a couple of days ago
that led me to a different understanding in this particular
case.
Andrew - kill this patch (unless you know better.)
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- From: [email protected] (Eric W. Biederman)
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- References:
- [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- From: Paul Jackson <[email protected]>
- Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- From: [email protected] (Eric W. Biederman)
- [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- Prev by Date: RAID5 initial rebuild slow, 2.6.16-rc4
- Next by Date: Question: how to map SCSI data DMA address to virtual address?
- Previous by thread: Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- Next by thread: Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c
- Index(es):
 |