Re: [patch] add private data to notifier_block

>>>>> "Kristen" == Kristen Accardi <[email protected]> writes:

Kristen> On Wed, 2006-03-22 at 14:04 -0500, Alan Stern wrote:
>> I still think this isn't really needed.  The same effect can be
>> accomplished by embedding a notifier_block struct within a larger
>> structure that also contains the data pointer.

Kristen> I thought of this, but felt it would make for less easy to
Kristen> read code.  But, that's just my personal style.

I'd have to vote for Alan's side here. Thats why we have the
containerof() stuff. It also means you can embed more than just a
pointer with the notifier block and it will generate more efficient
code when doing so.

Cheers,
Jes
-
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] add private data to notifier_block
    • From: Kristen Accardi <[email protected]>

• References:
  • Re: [patch] add private data to notifier_block
    • From: Alan Stern <[email protected]>
  • Re: [patch] add private data to notifier_block
    • From: Kristen Accardi <[email protected]>

• Prev by Date: Re: raw I/O support for Fedora Core 4
• Next by Date: Re: [PATCH 9 of 18] ipath - char devices for diagnostics and lightweight subnet management
• Previous by thread: Re: [patch] add private data to notifier_block
• Next by thread: Re: [patch] add private data to notifier_block
• 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]