From: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH 0/3] fix ia64 clocksource
Date: Mon, 23 Jul 2007 00:57:03 +0000 [thread overview]
Message-ID: <46A3FD94.90902@jp.fujitsu.com> (raw)
In-Reply-To: <469E2AAF.30705@jp.fujitsu.com>
Luck, Tony wrote:
>> I need to make the cleanups Tony identified. After that how would you like to
>> proceed? Combining your patch 1/3 and my 1/2 seems logical.
>
> I've done the cleanup, and merged Seto-san's parts 1,2,3 with your part 1, and
> updated it all for the tip of Linus' tree. Result is below.
>
> Part 2 stayed the same, except that I also deleted Documentation/time_interpolators.txt
>
> I'm going to send both to Linus later today ... so read fast and shout if
> I botched the merge.
No problem at all. Thanks!
Acked-by: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
H.Seto
prev parent reply other threads:[~2007-07-23 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 14:58 [PATCH 0/3] fix ia64 clocksource Hidetoshi Seto
2007-07-20 10:44 ` Bob Picco
2007-07-20 16:33 ` Luck, Tony
2007-07-20 16:55 ` Bob Picco
2007-07-23 0:57 ` Hidetoshi Seto [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=46A3FD94.90902@jp.fujitsu.com \
--to=seto.hidetoshi@jp.fujitsu.com \
--cc=linux-ia64@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