From: Jes Sorensen <jes@sgi.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [patch -mm] notifier chain initialization
Date: Wed, 22 Mar 2006 22:10:13 +0100 [thread overview]
Message-ID: <4421BD35.7070702@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0603221203210.5159-100000@iolanthe.rowland.org>
Alan Stern wrote:
>> The benefit is that one can use the FOO_NOTIFIER_INIT() macro for
>> static initialization of a notifier chain.
>
> You probably mean _dynamic_ initialization of a notifier head. The
> current code handles static initialization just fine.
Actually I meant static, I have a notifier declared within a struct and
a macro that initializes it at compile time - didn't work with the old
code.
But I also use it dynamically where this also benefits it.
> There's nothing wrong with doing things like this. I didn't include
> initialization macros originally simply because there aren't any
> dynamically-initialized notifier heads in the kernel.
There probably will be :)
Cheers,
Jes
prev parent reply other threads:[~2006-03-22 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 16:11 [patch -mm] notifier chain initialization Jes Sorensen
2006-03-22 17:05 ` Alan Stern
2006-03-22 21:10 ` Jes Sorensen [this message]
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=4421BD35.7070702@sgi.com \
--to=jes@sgi.com \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox