Re: 2.6.17-mm1: kernel/lockdep.c: write-only variables

* Adrian Bunk <[email protected]> wrote:

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

they are stale - i'll remove them. (there's a new calculation method for 
them)

	Ingo
-
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: 2.6.17-mm1: kernel/lockdep.c: write-only variables
    • From: Ingo Molnar <[email protected]>

• References:
  • 2.6.17-mm1
    • From: Andrew Morton <[email protected]>
  • 2.6.17-mm1: kernel/lockdep.c: write-only variables
    • From: Adrian Bunk <[email protected]>

• Prev by Date: Re: Dropping Packets in 2.6.17
• Next by Date: Re: [PATCH] mm/tracking dirty pages: update get_dirty_limits for mmap tracking
• Previous by thread: 2.6.17-mm1: kernel/lockdep.c: write-only variables
• Next by thread: Re: 2.6.17-mm1: kernel/lockdep.c: write-only variables
• 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]