summaryrefslogtreecommitdiffstats
path: root/fs/quota_v1.c
diff options
context:
space:
mode:
authorGuennadi Liakhovetski <g.liakhovetski@gmx.de>2007-05-17 18:56:32 +1000
committerPaul Mackerras <paulus@samba.org>2007-06-25 16:58:07 +1000
commit1a06e0fe96526e43bab90fbab2263b55fb3d45d1 (patch)
tree14987db825941f75ddf2e2bff6ac434f9e4fb5d4 /fs/quota_v1.c
parent8fa336d889caa72637e0860f53fa40ef66dcceaf (diff)
downloadlinux-1a06e0fe96526e43bab90fbab2263b55fb3d45d1.tar.bz2
[POWERPC] Don't link timer.o for powerpc systems using generic rtc
With both generic rtc and powerpc timer suspend / resume code now in the (powerpc.git) tree, powerpc platforms using the generic timer and enabling power management will have timer.o linked in the kernel, which they don't need. Moreover, it will likely WARN_ON(!ppc_md.get_rtc_time), save zero-time and return no error on suspend... As a possible solution we can choose not to build timer.o when RTC_CLASS is enabled. However, I can imagine systems with 2 rtc's, one served by the ppc-rtc, another one generic built as a module, in which case using the ppc-rtc for suspend / resume will be impossible. Not to say, that such a configuration would be ugly... Signed-off-by: G. Liakhovetski <g.liakhovetski@gmx.de> Signed-off-by: Paul Mackerras <paulus@samba.org>
Diffstat (limited to 'fs/quota_v1.c')
0 files changed, 0 insertions, 0 deletions