From: Tejun Heo <htejun@gmail.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Jeff Garzik <jgarzik@pobox.com>,
Ash Willis <ashwillis@programmer.net>,
linux-pcmcia@lists.infradead.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 3/3] Makes lguest's irq handler typesafe
Date: Sat, 19 Jan 2008 13:08:28 +0900 [thread overview]
Message-ID: <479177BC.8030200@gmail.com> (raw)
In-Reply-To: <200801191459.49735.rusty@rustcorp.com.au>
Hello,
Rusty Russell wrote:
> There are three possibilities: (1) force everyone to use void *, (2) force
> everyone to be type-correct, (3) allow both with some tricks. Currently
> we're on (1). For kthread, with only dozens of users, I chose (2) (very
> simple, easy to understand). I think for widespread things like timer and
> interrupt handlers, I think (3) is the right way to go.
Yeah, during transition, we definitely want (3).
> I wanted to get this patch out there and see what the reaction was. I can
> do timers next, if that's going to add fuel to the discussion.
I think you successfully got a very small sample of possible reactions.
Jeff vetoing it (and for good reasons) and me a bit more positive but
not quite sold. Yeah, I think we need a good flame war to determine our
heading and converting timer shouldn't take too much of your time, right?
Thanks.
--
tejun
next prev parent reply other threads:[~2008-01-19 4:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 20:22 [PATCH 1/3] Improve type handling in interrupt handlers Rusty Russell
2008-01-18 20:25 ` [PATCH 2/3] Make IRQ handlers typesafe Rusty Russell
2008-01-18 20:27 ` [PATCH 3/3] Makes lguest's irq handler typesafe Rusty Russell
2008-01-18 20:45 ` Jeff Garzik
2008-01-18 22:17 ` Rusty Russell
2008-01-18 22:17 ` Rusty Russell
2008-01-18 20:45 ` Jeff Garzik
2008-01-18 23:12 ` Tejun Heo
2008-01-19 1:28 ` Rusty Russell
2008-01-19 1:28 ` Rusty Russell
2008-01-19 1:40 ` Tejun Heo
2008-01-19 1:44 ` Tejun Heo
2008-01-19 3:59 ` Rusty Russell
2008-01-19 4:08 ` Tejun Heo [this message]
2008-01-19 23:27 ` Rusty Russell
2008-01-19 23:27 ` Rusty Russell
2008-01-19 4:08 ` Tejun Heo
2008-01-19 3:59 ` Rusty Russell
2008-01-19 1:44 ` Tejun Heo
2008-01-19 1:40 ` Tejun Heo
2008-01-18 23:12 ` Tejun Heo
2008-01-18 20:27 ` Rusty Russell
2008-01-18 20:43 ` [PATCH 2/3] Make IRQ handlers typesafe Jeff Garzik
2008-01-18 20:43 ` Jeff Garzik
2008-01-18 20:25 ` Rusty Russell
2008-01-18 20:41 ` [PATCH 1/3] Improve type handling in interrupt handlers Jeff Garzik
2008-01-18 22:11 ` Rusty Russell
2008-01-18 22:54 ` Jeff Garzik
2008-01-19 1:29 ` 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=479177BC.8030200@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ashwillis@programmer.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=rusty@rustcorp.com.au \
--cc=virtualization@lists.linux-foundation.org \
/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.