linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] export new __io{re,un}map_at() symbols
Date: Tue, 11 Sep 2007 09:10:20 +1000	[thread overview]
Message-ID: <18149.52956.875510.937857@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <20070910224136.GA28808@lixom.net>

Olof Johansson writes:

> electra_cf uses it, that driver is currently in -mm including below
> update to use benh's rewritten interfaces:
> 
> http://patchwork.ozlabs.org/linuxppc/patch?id=13237
> 
> It gets the effective addresses to use out of the device tree.

Huh?  What does firmware (or the device tree) know about how the
kernel uses effective addresses?

Paul.

  reply	other threads:[~2007-09-10 23:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31  3:58 [PATCH] export new __io{re,un}map_at() symbols Olof Johansson
2007-09-10 21:57 ` Paul Mackerras
2007-09-10 22:41   ` Olof Johansson
2007-09-10 23:10     ` Paul Mackerras [this message]
2007-09-10 23:34       ` Olof Johansson

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=18149.52956.875510.937857@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=olof@lixom.net \
    /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).