2.6.17-mm1: kernel/lockdep.c: write-only variables
- From: Adrian Bunk <bunk@xxxxxxxxx>
- Date: Thu, 22 Jun 2006 17:52:30 +0200
The following variables in kernel/lockdep.c are write-only:
nr_hardirq_read_safe_locks
nr_hardirq_read_unsafe_locks
nr_hardirq_safe_locks
nr_hardirq_unsafe_locks
nr_softirq_read_safe_locks
nr_softirq_read_unsafe_locks
nr_softirq_safe_locks
nr_softirq_unsafe_locks
Is a usage pending or should they be removed?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: 2.6.17-mm1: kernel/lockdep.c: write-only variables
- From: Ingo Molnar
- Re: 2.6.17-mm1: kernel/lockdep.c: write-only variables
- References:
- 2.6.17-mm1
- From: Andrew Morton
- 2.6.17-mm1
- Prev by Date: Re: [PATCH -mm 6/6] cpu_relax(): ptrace.c coding style fix
- Next by Date: Re: 2.6.17-mm1
- Previous by thread: Re: 2.6.17-mm1
- Next by thread: Re: 2.6.17-mm1: kernel/lockdep.c: write-only variables
- Index(es):
Relevant Pages
|
