mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: "landley@trommello.org" <landley@trommello.org>,
	Jim Houston <jim.houston@ccur.com>, "ak@suse.de" <ak@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	high-res-timers-discourse@lists.sourceforge.net
Subject: Re: [PATCH 1/3] High-res-timers part 1 (core) take 7
Date: Mon, 28 Oct 2002 22:16:27 -0800	[thread overview]
Message-ID: <3DBE27BB.E1A99E6@mvista.com> (raw)
In-Reply-To: <1035849209.1157.242.camel@dell_ss3.pdx.osdl.net>

Stephen Hemminger wrote:
> 
> This patch does not apply cleanly against 2.5.44.
> 
>   ------------------------------------------------------------
>                   Name: timer.c.rej
>    timer.c.rej    Type: application/x-reject
>               Encoding: base64

I suspect that you did not apply the posix patch first.  Did
you see:
"This patch depends on the
POSIX clocks & timers patch in that it assumes the changes
that patch made to timer.c to remove timer_t.  This
dependency can be removed if needed."

in the referenced posting?  

The POSIX patch needed to remove timer_t as it is the type
the standard uses for a timer id where as timer.c was/is
using it to refer to a timer_struct.  I had to choose an
application order (or make yet another patch that would need
to preceed application of either of them :(.

I choose this order, but it can be changed if that is what
is desired.  My choice was made because I think the POSIX
clocks & timers API is more important than high-res.  It is
usable without high-res, however, high-res is of little use
with out the POSIX API patch.

If you did apply the posix patch prior to this one and still
have this failure, please do let me know.


-- 
George Anzinger   george@mvista.com
High-res-timers: 
http://sourceforge.net/projects/high-res-timers/
Preemption patch:
http://www.kernel.org/pub/linux/kernel/people/rml

      reply	other threads:[~2002-10-29  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 20:01 george anzinger
2002-10-28 23:53 ` Stephen Hemminger
2002-10-29  6:16   ` george anzinger [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=3DBE27BB.E1A99E6@mvista.com \
    --to=george@mvista.com \
    --cc=ak@suse.de \
    --cc=high-res-timers-discourse@lists.sourceforge.net \
    --cc=jim.houston@ccur.com \
    --cc=landley@trommello.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shemminger@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

Powered by JetHome