Re: [PATCH] Proc: move proc fs hooks from cpuset.c to proc/fs/base.c

> Seems pointless.  This just increases #ifdef churn for no gain.

Take a look at fs/proc/base.c.  That's how pretty much all the
other proc hooks are done, with ifdef's around their proc hooks.

ifdef minimization is a good goal, yes.

But uniformity of practice is another good goal.

-- 
                  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)

• 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]>

• Prev by Date: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
• Next by Date: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
• 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):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]