From: john stultz <johnstul@us.ibm.com>
To: Peter Keilty <peter.keilty@hp.com>
Cc: linux-ia64@vger.kernel.org, Eric Whitney <eric.whitney@hp.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] ia64: convert to use clocksource code
Date: Wed, 02 May 2007 10:50:01 -0700 [thread overview]
Message-ID: <1178128202.6183.1.camel@localhost.localdomain> (raw)
In-Reply-To: <4631F26D.7080404@hp.com>
On Fri, 2007-04-27 at 08:54 -0400, Peter Keilty wrote:
> john stultz wrote:
> >On Thu, 2007-04-26 at 16:26 -0400, Peter Keilty wrote:
> >>From: Peter Keilty <peter.keilty@hp.com>
> >>
> >>Initial ia64 conversion to the generic timekeeping/clocksource code.
> >>
> >>Signed-off-by: Peter Keilty <peter.keilty@hp.com>
> >>Signed-off-by: John Stultz <johnstul@us.ibm.com>
> >>
> > Thanks so much for pushing this on! I suspect this patch needs to be
> >updated a touch, as I'm not sure if it still compiles in light of recent
> >changes...
> >
> You are correct, you need patch 3/3 for it to compile and run.
> I did a patch to the orginal patch, thought that was correct thing to do.
> But I can make a new patch 1 from the orginal of ours and my #3.
> I would also make an update to the #2 patch from #3 for ntp correct change.
> That would be just 2 patches then, the enable_ia64 and remove_interpolater.
> What do you think?
Yep. That sounds like the right path to me. Its a good idea to make sure
your patch set compiles each step of the way, so later folks can
properly bisect through it looking for other issues.
thanks
-john
next prev parent reply other threads:[~2007-05-02 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 20:26 [PATCH 1/3] ia64: convert to use clocksource code Peter Keilty
2007-04-26 20:27 ` [PATCH 2/3] ia64: remove interpolater code Peter Keilty
2007-04-26 20:52 ` john stultz
2007-04-26 21:47 ` David Miller
2007-04-26 20:27 ` [PATCH 3/3] ia64: update fsyscall for performance, enable build/run on 2.6.21-rc1 Peter Keilty
2007-04-26 20:41 ` [PATCH 1/3] ia64: convert to use clocksource code Sam Ravnborg
2007-04-26 20:48 ` john stultz
2007-04-26 21:07 ` Daniel Walker
2007-04-27 14:38 ` Peter Keilty
2007-04-27 15:35 ` Daniel Walker
2007-04-27 15:42 ` Peter Keilty
2007-04-27 15:48 ` Daniel Walker
2007-04-27 16:11 ` Peter Keilty
2007-04-27 16:32 ` Daniel Walker
2007-05-02 17:58 ` john stultz
2007-05-02 19:08 ` Daniel Walker
2007-04-26 21:18 ` john stultz
2007-04-27 12:54 ` Peter Keilty
2007-05-02 17:50 ` john stultz [this message]
2007-04-27 1:02 ` Chris Wright
2007-04-27 13:35 ` Peter Keilty
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=1178128202.6183.1.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=eric.whitney@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.keilty@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox