From: Komal Shah <komal_shah802003@yahoo.com>
To: linux-omap-open-source@linux.omap.com
Subject: [PATCH] OMAP: FB: Use blocking notifier apis
Date: Tue, 28 Mar 2006 01:03:40 -0800 (PST) [thread overview]
Message-ID: <20060328090340.98259.qmail@web32910.mail.mud.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
Imre/Tony,
Attached patch should be applied only after omap git tree is synched
with linus mainline tree as of today.
I have use blocking notifiers.
---Komal Shah
http://komalshah.blogspot.com/
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
[-- Attachment #2: 451432436-0001-OMAP-FB-Move-to-new-notifier-apis.txt --]
[-- Type: text/plain, Size: 1767 bytes --]
>From nobody Mon Sep 17 00:00:00 2001
From: Komal Shah <komal_shah802003@yahoo.com>
Date: Tue Mar 28 11:57:53 2006 +0300
Subject: [PATCH] OMAP: FB: Move to new notifier apis.
Signed-off-by: Komal Shah <komal_shah802003@yahoo.com>
---
drivers/video/omap/omapfb_main.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
a64117837ac59721e3bb62827e1b4742b17aa7c1
diff --git a/drivers/video/omap/omapfb_main.c b/drivers/video/omap/omapfb_main.c
index d32ba58..546e60d 100644
--- a/drivers/video/omap/omapfb_main.c
+++ b/drivers/video/omap/omapfb_main.c
@@ -687,7 +687,7 @@
return r;
}
-static struct notifier_block *omapfb_client_list;
+static BLOCKING_NOTIFIER_HEAD(omapfb_client_list);
int omapfb_register_client(struct omapfb_notifier_block *omapfb_nb,
omapfb_notifier_callback_t callback,
@@ -700,7 +700,7 @@
omapfb_nb->nb.notifier_call = (int (*)(struct notifier_block *,
unsigned long, void *))callback;
omapfb_nb->data = callback_data;
- r = notifier_chain_register(&omapfb_client_list, &omapfb_nb->nb);
+ r = blocking_notifier_chain_register(&omapfb_client_list, &omapfb_nb->nb);
if (r)
return r;
if (omapfb_dev != NULL &&
@@ -714,7 +714,7 @@
int omapfb_unregister_client(struct omapfb_notifier_block *omapfb_nb)
{
- return notifier_chain_unregister(&omapfb_client_list,
+ return blocking_notifier_chain_unregister(&omapfb_client_list,
&omapfb_nb->nb);
}
EXPORT_SYMBOL(omapfb_unregister_client);
@@ -722,7 +722,7 @@
void omapfb_notify_clients(struct omapfb_device *fbdev, unsigned long event)
{
DBGENTER(1);
- notifier_call_chain(&omapfb_client_list, event, fbdev);
+ blocking_notifier_call_chain(&omapfb_client_list, event, fbdev);
}
EXPORT_SYMBOL(omapfb_notify_clients);
--
1.3-rc1.GIT
[-- Attachment #3: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2006-03-28 9:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060328090340.98259.qmail@web32910.mail.mud.yahoo.com \
--to=komal_shah802003@yahoo.com \
--cc=linux-omap-open-source@linux.omap.com \
/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