public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: davidm@hpl.hp.com, davidm@napali.hpl.hp.com
Cc: akpm@digeo.com, ak@muc.de, arjanv@redhat.com,
	johnstul@us.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: time interpolation hooks
Date: Mon, 19 May 2003 15:37:58 -0700 (PDT)	[thread overview]
Message-ID: <20030519.153758.71094061.davem@redhat.com> (raw)
In-Reply-To: <16073.5555.158600.61609@napali.hpl.hp.com>

   From: David Mosberger <davidm@napali.hpl.hp.com>
   Date: Mon, 19 May 2003 10:34:43 -0700

   >>>>> On 16 May 2003 19:38:01 -0700, "David S. Miller" <davem@redhat.com> said:
   
     DaveM> I think Andrew is really suggesting to declare these two
     DaveM> things in an arch header, so if one needs it to be a function
     DaveM> pointer one can make it so.
   
   I don't think this should be (purely) an arch thing.  It's just as
   much a driver issue.  For example, HPET will pretty much work the same
   on x86 and ia64, so being able to have a shared "driver" would be
   useful.  I agree though that it would be nice if arches that don't
   care for time-interpolation at all could turn it off completely.
   In the proposal below, an architecture could achieve that by turning
   off CONFIG_TIME_INTERPOLATION.

That's not the issue, if I have only ONE way to do this on my
platform, I can INLINE this thing and I DO NOT need function
pointers.

I should have that option.

  parent reply	other threads:[~2003-05-19 22:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 21:23 time interpolation hooks Andrew Morton
2003-05-16 22:00 ` David Mosberger
2003-05-17  2:38   ` David S. Miller
2003-05-19 17:34     ` David Mosberger
2003-05-19 17:42       ` Arjan van de Ven
2003-05-19 18:35         ` David Mosberger
2003-05-19 18:57           ` Andrew Morton
2003-05-20  7:26             ` David Mosberger
2003-05-19 22:37       ` David S. Miller [this message]
2003-05-19 23:03         ` David Mosberger
2003-05-19 23:08           ` David S. Miller
2003-05-17  9:09 ` Arjan van de Ven
2003-05-17 16:31 ` john stultz
2003-05-17 16:37   ` john stultz

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=20030519.153758.71094061.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=ak@muc.de \
    --cc=akpm@digeo.com \
    --cc=arjanv@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=davidm@napali.hpl.hp.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox