From: Doug Chapman <doug.chapman@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH 1/2] ia64 clocksource
Date: Thu, 19 Jul 2007 16:31:48 +0000 [thread overview]
Message-ID: <1184862708.3825.14.camel@dchapman.boston.redhat.com> (raw)
In-Reply-To: <20070714002509.GJ2317@localhost>
On Mon, 2007-07-16 at 14:33 -0700, Luck, Tony wrote:
> On the subject of whether to push into 2.6.23 or cook in -mm until
> 2.6.24 ... I'm not sure how much benefit we'd get from the delay.
> Anyone want to stand up and be counted as running serious testing
> on -mm kernels on ia64? I fear that the amount of extra testing
> that we'd get is really quite small. 2.6.23-rc1 is only a week away,
> and this code is very subtle in places ... I'm nervous about this.
I have been doing testing out of your ia64 git and linus's git trees on
our HP hardware. I am thinking adding -mm would certainly be
worthwhile.
- Doug
prev parent reply other threads:[~2007-07-19 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 0:25 [PATCH 1/2] ia64 clocksource Bob Picco
2007-07-14 10:25 ` Christoph Hellwig
2007-07-16 10:07 ` Bob Picco
2007-07-16 21:33 ` Luck, Tony
2007-07-17 10:55 ` Hidetoshi Seto
2007-07-17 22:31 ` Bob Picco
2007-07-17 22:50 ` john stultz
2007-07-18 9:27 ` Hidetoshi Seto
2007-07-19 16:31 ` Doug Chapman [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=1184862708.3825.14.camel@dchapman.boston.redhat.com \
--to=doug.chapman@hp.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