From: Jesse Barnes <jbarnes@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Patch] Altix patch 012-huberror for 2.6.10
Date: Tue, 19 Oct 2004 23:05:48 +0000 [thread overview]
Message-ID: <200410191605.49033.jbarnes@engr.sgi.com> (raw)
In-Reply-To: <Pine.SGI.3.96.1041019151446.144128E-100000@fsgi900.americas.sgi.com>
On Tuesday, October 19, 2004 1:52 pm, Luck, Tony wrote:
> I've applied up to and including the 012 patch and pushed
> the whole thing up to the new tree on bkbits:
>
> http://lia64.bkbits.net/linux-ia64-release-2.6.10
>
> So you should pull from there and make sure it all builds
> for you before I send the "please do a bk pull" message to
> Linus. Please send me an ACK when you've tested it.
ACK. I've tested it on a small system and it comes up ok. I'll run it
through sparse and do some more testing tomorrow (and I'm sure Pat will too),
but I'd say it's ok for Linus to pull at this point. We'll no doubt run into
a few small things, but those will have to get fixed anyway, no reason to
hold up wider testing.
Thanks,
Jesse
prev parent reply other threads:[~2004-10-19 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 20:23 [Patch] Altix patch 012-huberror for 2.6.10 Pat Gefre
2004-10-19 20:52 ` Luck, Tony
2004-10-19 23:05 ` Jesse Barnes [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=200410191605.49033.jbarnes@engr.sgi.com \
--to=jbarnes@engr.sgi.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