From: Kristen Accardi <kristen.c.accardi@intel.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] add private data to notifier_block
Date: Wed, 22 Mar 2006 13:00:11 -0800 [thread overview]
Message-ID: <1143061212.8924.10.camel@whizzy> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0603221402070.7453-100000@iolanthe.rowland.org>
On Wed, 2006-03-22 at 14:04 -0500, Alan Stern wrote:
> On Tue, 21 Mar 2006, Kristen Accardi wrote:
>
> > While most current uses of notifier_block use a global struct, I would
> > like to be able to use it on a per device basis for drivers which have
> > multiple device instances. I would also like to be able to have a
> > private data struct associated with the notifier block so that per
> > device data can be easily accessed. This patch will modify the
> > notifier_block struct to add a void *, and will require no modifications
> > to any other users of the notifier_block.
> >
> > Signed-off-by: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
> >
> > ---
> > include/linux/notifier.h | 1 +
> > 1 files changed, 1 insertion(+)
> >
> > --- 2.6-git-kca.orig/include/linux/notifier.h
> > +++ 2.6-git-kca/include/linux/notifier.h
> > @@ -15,6 +15,7 @@ struct notifier_block
> > {
> > int (*notifier_call)(struct notifier_block *self, unsigned long, void *);
> > struct notifier_block *next;
> > + void *data;
> > int priority;
> > };
>
> 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.
>
I thought of this, but felt it would make for less easy to read code.
But, that's just my personal style.
> On the other hand this isn't a terribly big change, so I don't actually
> object to it.
>
Thanks.
> Alan Stern
next prev parent reply other threads:[~2006-03-22 20:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 19:42 [patch] add private data to notifier_block Kristen Accardi
2006-03-22 18:00 ` Zach Brown
2006-03-22 19:04 ` Alan Stern
2006-03-22 21:00 ` Kristen Accardi [this message]
2006-03-23 10:06 ` Jes Sorensen
2006-03-23 18:01 ` Kristen Accardi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1143061212.8924.10.camel@whizzy \
--to=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.