From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: [PATCH] A BTFIXUP'd fix for pte_read()
Date: Thu, 03 Feb 2005 00:55:41 +0000 [thread overview]
Message-ID: <20050203005541.GF24805@holomorphy.com> (raw)
In-Reply-To: <20050202200409.GA30839@artsapartment.org>
On Wed, 2 Feb 2005 14:40:19 -0800 William Lee Irwin III <wli@holomorphy.com> wrote:
>> Doing a quick doublecheck to be sure this actually applies before
>> shipping upstream. Sorry about the delay, folks.
On Wed, Feb 02, 2005 at 03:32:21PM -0800, David S. Miller wrote:
> I disagree with Tom's patch in that it puts this huge switch()
> statement inline. The whole point of BTFIXUP_HIGH() is that it
> resolves the call to a single instruction which can be easily
> patched at runtime.
> If it's going to expand to multiple BTFIXUP_HIGH() calls and a
> switch statement, just make it a normal BTFIXUP() to a function
> and place the implementation in sun4c.c and sun4m.c
I'm on the road and people are antsy for something that builds, so
I'm rather tempted to take it for expedience and properly BTFIXUP-ize
it after 2.6.11, which appears rather imminent, since I basically
won't push anything I've written myself but not tested. What I have in
terms of remote access I've lost for want of time. There's also
something of a reluctance to resynch before 2.6.11 out of disgust for
certain changes and/or the manner in which they were merged.
Maybe I can cook something better up before my return flight while at
the airport, though I'd be glad to see spot or ahaas get done before me.
-- wli
next prev parent reply other threads:[~2005-02-03 0:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-02 20:04 [PATCH] A BTFIXUP'd fix for pte_read() Art Haas
2005-02-02 21:54 ` Tom 'spot' Callaway
2005-02-02 22:40 ` William Lee Irwin III
2005-02-02 23:32 ` David S. Miller
2005-02-03 0:52 ` David S. Miller
2005-02-03 0:55 ` William Lee Irwin III [this message]
2005-02-03 4:22 ` Tom 'spot' Callaway
2005-02-03 6:27 ` David S. Miller
2005-02-03 9:13 ` William Lee Irwin III
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=20050203005541.GF24805@holomorphy.com \
--to=wli@holomorphy.com \
--cc=sparclinux@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.