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: [PULL] typesafe callbacks
Date: Tue, 15 Jul 2008 13:10:26 +1000 [thread overview]
Message-ID: <200807151310.26412.rusty@rustcorp.com.au> (raw)
As featured in linux-next for at least two full revs, and posted here.
Allows (but doesn't require) various callbacks to be the correct type
instead of void *.
kthread and timers for the moment, stop_machine and request_irq are
blocked pending textual clashes.
Added __attribute__((printf)) to kthread_create to this batch: textual
conflicts otherwise.
Thanks,
Rusty.
===
The following changes since commit 50515af207d410c9f228380e529c56f43c3de0bd:
David Woodhouse (1):
firmware: Correct dependency on CONFIG_EXTRA_FIRMWARE_DIR
are available in the git repository at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-for-linus.git master
Rusty Russell (5):
cast_if_type: allow macros functions which take more than one type.
typesafe_cb: wrappers for typesafe callbacks.
Label kthread_create() with printf attribute tag.
typesafe: kthread_create and kthread_run
typesafe: TIMER_INITIALIZER and setup_timer
include/linux/compiler-gcc.h | 18 ++++++++++++++++++
include/linux/compiler-intel.h | 2 ++
include/linux/kernel.h | 35 +++++++++++++++++++++++++++++++++++
include/linux/kthread.h | 29 ++++++++++++++++++++++++++---
include/linux/timer.h | 32 +++++++++++++++++++++++---------
kernel/kthread.c | 29 +++++------------------------
6 files changed, 109 insertions(+), 36 deletions(-)
reply other threads:[~2008-07-15 3:11 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=200807151310.26412.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.