Re: [PATCH] Pass sparse the lock expression given to lock annotations

On Thu, 24 Aug 2006 17:48:56 -0700
Josh Triplett <[email protected]> wrote:

> The lock annotation macros __acquires, __releases, __acquire, and __release
> all currently throw the lock expression passed as an argument.  Now that
> sparse can parse __context__ and __attribute__((context)) with a context
> expression, pass the lock expression down to sparse as the context expression.

What is the dependency relationship between your kernel changes and your
proposed change to sparse?

-
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] Pass sparse the lock expression given to lock annotations
    • From: Josh Triplett <[email protected]>

• References:
  • [PATCH] Pass sparse the lock expression given to lock annotations
    • From: Josh Triplett <[email protected]>

• Prev by Date: Re: Unnecessary Relocation Hiding?
• Next by Date: Re: [PATCH 2.6.9-34.0.1.EL] hid-core.c: Add GTCO CalComp PIDs to blacklist
• Previous by thread: [PATCH] Pass sparse the lock expression given to lock annotations
• Next by thread: Re: [PATCH] Pass sparse the lock expression given to lock annotations
• 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]