All of lore.kernel.org
 help / color / mirror / Atom feed
From: george anzinger <george@mvista.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] High-res-timers part 2 (x86 platform code) take 21
Date: Fri, 20 Dec 2002 21:53:20 -0800	[thread overview]
Message-ID: <3E0401D0.9EF68E64@mvista.com> (raw)
In-Reply-To: Pine.LNX.4.33L2.0212201641210.1703-100000@dragon.pdx.osdl.net

Thanks for the heads up.  A new patch is now posted.

-g


"Randy.Dunlap" wrote:
> 
> On Fri, 20 Dec 2002, george anzinger wrote:
> 
> | This is the platform part of the high-res timers for the
> | x86.
> |
> | Changes since last time:
> | CONFIG dependency added to not turn on stuff only needed
> | when CONFIG_HIGH_RES = y.
> | ----------
> |
> | The 3 parts to the high res timers are:
> |  core         The core kernel (i.e. platform independent) changes
> | *i386         The high-res changes for the i386 (x86) platform
> |  hrposix      The changes to the POSIX clocks & timers patch to
> | use high-res timers
> |
> | Please apply.
> 
> George,
> 
> This arch/i386/Kconfig file contains some KGDB options that keep
> it from applying cleanly.  Not delaying me, but it might delay someone.
> 
> $ patch -p1 -b --dry-run < ~/cglstage/HRT_2002_1220/03-hrtimers-x86.patch
> patching file arch/i386/Kconfig
> Hunk #2 FAILED at 1665.
> Hunk #3 FAILED at 1857.
> Hunk #4 FAILED at 1866.
> 3 out of 4 hunks FAILED -- saving rejects to file arch/i386/Kconfig.rej
> 
> --
> ~Randy

-- 
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-12-21  5:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-20  9:52 [PATCH 2/3] High-res-timers part 2 (x86 platform code) take 21 george anzinger
2002-12-21  0:43 ` Randy.Dunlap
2002-12-21  5:53   ` 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=3E0401D0.9EF68E64@mvista.com \
    --to=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --cc=torvalds@transmeta.com \
    /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.