From: Rusty Russell <rusty@rustcorp.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: [PATCH 0/4] typesafe callbacks
Date: Fri, 25 Jul 2008 12:13:17 +1000 [thread overview]
Message-ID: <200807251213.17773.rusty@rustcorp.com.au> (raw)
It's possible to portably make callbacks typesafe, as well as taking the
existing void * arg. This makes the callers more readable and more typesafe.
Done in a way that doesn't break non-gcc: they just don't get a warning.
Been in linux-next for about two full cycles now, and I really want to start
using this in my own code.
Thanks,
Rusty.
next reply other threads:[~2008-07-25 2:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 2:13 Rusty Russell [this message]
2008-07-25 2:14 ` [PATCH 1/4] typesafe: cast_if_type: allow macros functions which take more than one type Rusty Russell
2008-07-25 2:16 ` [PATCH 2/4] typesafe: typesafe_cb: wrappers for typesafe callbacks Rusty Russell
2008-07-25 2:17 ` [PATCH 3/4] typesafe: kthread_create and kthread_run Rusty Russell
2008-07-25 2:19 ` [PATCH 4/4] typesafe: TIMER_INITIALIZER and setup_timer Rusty Russell
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=200807251213.17773.rusty@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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.