From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paolo Galtieri <pgaltieri@mvista.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Two bugs in handling of highmem on PPC
Date: Fri, 07 Oct 2005 10:54:40 +1000 [thread overview]
Message-ID: <1128646480.17365.7.camel@gaston> (raw)
In-Reply-To: <1128639689.4809.19.camel@playin.mvista.com>
>
> I would very much appreciate it if those of you who are more familiar
> with this part of the kernel could review and comment on my
> interpretation of what is going on and provide feedback.
While the first bit of your patch makes some sense, the second one
doesn't at all to me, you must be missing something there...
Ben
prev parent reply other threads:[~2005-10-07 0:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 23:01 Two bugs in handling of highmem on PPC Paolo Galtieri
2005-10-07 0:54 ` Benjamin Herrenschmidt [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=1128646480.17365.7.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=pgaltieri@mvista.com \
/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;
as well as URLs for NNTP newsgroup(s).