mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roland McGrath <roland@redhat.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
	linux-kernel@vger.kernel.org, george@mvista.com
Subject: Re: [PATCH 4/7] posix-timers: CPU clock support for POSIX timers
Date: Tue, 25 Jan 2005 15:17:57 -0800	[thread overview]
Message-ID: <200501252317.j0PNHvE5014057@magilla.sf.frob.com> (raw)
In-Reply-To: Christoph Lameter's message of  Tuesday, 25 January 2005 14:52:56 -0800 <Pine.LNX.4.58.0501251450080.26368@schroedinger.engr.sgi.com>

> Your patch breaks the mmtimer driver because it used k_itimer values for
> its own purposes. Here is a fix by defining an additional structure
> in k_itimer (same approach for mmtimer as the cpu timers):

This seems reasonable enough to me.  Perhaps if there will be lots of timer
guts implementations, and more coming in modules or whatnot, then the union
should be replaced with a more generic private-data buffer, or at least
have a vanilla padding alternative in the union.  But I am certainly happy
with the simple path of just adding in the implementations as they come
like you've done for mmtimer.


Thanks,
Roland

  reply	other threads:[~2005-01-26  1:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 23:25 Roland McGrath
2005-01-25  2:31 ` George Anzinger
2005-01-25  2:35   ` Christoph Lameter
2005-01-25 22:52     ` Christoph Lameter
2005-01-25 23:17       ` Roland McGrath [this message]
2005-01-25 23:39       ` George Anzinger
2005-01-25 23:48         ` Christoph Lameter
2005-01-26  1:04         ` Chris Wedgwood
2005-01-25 23:15   ` Roland McGrath

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=200501252317.j0PNHvE5014057@magilla.sf.frob.com \
    --to=roland@redhat.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®