All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Tejun Heo <htejun@gmail.com>
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 14:59:49 +1100	[thread overview]
Message-ID: <200801191459.49735.rusty@rustcorp.com.au> (raw)
In-Reply-To: <47915614.7080608@gmail.com>

On Saturday 19 January 2008 12:44:52 Tejun Heo wrote:
> Tejun Heo wrote:
> > so I think the question is "do we want to change all callbacks to
> > take native pointer type instead of void pointer?".
>
> Lemme clarity myself a bit.  I'm not saying that we should convert all
> at once or literally every callback should be converted.  What I'm
> saying is whether we're headed that way in general and converting big
> ones - timer for example - and getting the conversion agreed upon should
> be enough to set the norm.

Hi Tejun

    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.

    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.

Thanks!
Rusty.

  parent reply	other threads:[~2008-01-19  4:00 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:25 ` Rusty Russell
2008-01-18 20:27   ` [PATCH 3/3] Makes lguest's irq handler typesafe Rusty Russell
2008-01-18 20:27   ` 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  3:59             ` Rusty Russell [this message]
2008-01-19  4:08               ` Tejun Heo
2008-01-19  4:08               ` Tejun Heo
2008-01-19 23:27                 ` Rusty Russell
2008-01-19 23:27                 ` 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:43   ` [PATCH 2/3] Make IRQ handlers typesafe Jeff Garzik
2008-01-18 20:43   ` Jeff Garzik
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=200801191459.49735.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@linux-foundation.org \
    --cc=ashwillis@programmer.net \
    --cc=htejun@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pcmcia@lists.infradead.org \
    --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.