From: Christopher Wedgwood <cw@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [PATCH] (2.6.0-test1 bk) ivt rearrangement and sn2-specific boot-time replacement code
Date: Thu, 17 Jul 2003 18:23:17 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105846640513473@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105840587916478@msgid-missing>
On Thu, Jul 17, 2003 at 11:04:14AM -0700, David Mosberger wrote:
> Screams don't transmit well over the Internet. But I assure you,
> there were there nonetheless...
> Please see Bjorn's comment about the patch.
Actually, for this patch there were no nasty comments :)
I had hoped this really wouldn't be a problem for most people as all
I'm doing is moving some code about and changing a symbol name.
I've been running this for months in one form or another on on hp and
intel hardware too.
I guess it goes without saying whatever objections people have I'll
address promptly so long as I hear them.
Thanks,
--cw
prev parent reply other threads:[~2003-07-17 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 1:37 [PATCH] (2.6.0-test1 bk) ivt rearrangement and sn2-specific boot-time replacement code Christopher Wedgwood
2003-07-17 18:04 ` David Mosberger
2003-07-17 18:23 ` Christopher Wedgwood [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=marc-linux-ia64-105846640513473@msgid-missing \
--to=cw@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 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.