From: Pavel Machek <pavel@suse.cz>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Peter Moulder <Peter.Moulder@infotech.monash.edu.au>,
Andi Kleen <ak@suse.de>, Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [RFC] typesafe callbacks?
Date: Tue, 12 Aug 2008 19:56:36 +0200 [thread overview]
Message-ID: <20080812175635.GA6153@ucw.cz> (raw)
In-Reply-To: <200808111756.21850.rusty@rustcorp.com.au>
Hi!
> Well, noone else voiced great enthusiasm about typesafe callbacks. I esp.
> like them because we can use them to wean off unsigned long in timer
> callbacks without a flag day.
>
> Should I just drop these patches, or leave them in -next for a third round?
> Rusty.
I think it is a great idea..
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-08-13 12:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 7:56 [RFC] typesafe callbacks? Rusty Russell
2008-08-12 17:56 ` Pavel Machek [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=20080812175635.GA6153@ucw.cz \
--to=pavel@suse.cz \
--cc=Peter.Moulder@infotech.monash.edu.au \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox