From: "Stephen Neuendorffer" <stephen.neuendorffer@xilinx•com>
To: "David Gibson" <david@gibson•dropbear.id.au>
Cc: linuxppc-dev@ozlabs•org
Subject: RE: [PATCH] [POWERPC] [v2] Improved documentation of device tree'ranges'.
Date: Mon, 3 Dec 2007 21:27:08 -0800 [thread overview]
Message-ID: <20071204053148.C2FBCF00059@mail199-blu.bigfish.com> (raw)
In-Reply-To: 20071204024025.GG32577@localhost.localdomain
[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]
I'm actually a little embarrassed that I didn't pick that nit myself.. :)
-----Original Message-----
From: David Gibson [mailto:david@gibson•dropbear.id.au]
Sent: Mon 12/3/2007 6:40 PM
To: Stephen Neuendorffer
Cc: grant.likely@secretlab•ca; linuxppc-dev@ozlabs•org
Subject: Re: [PATCH] [POWERPC] [v2] Improved documentation of device tree'ranges'.
On Mon, Dec 03, 2007 at 05:08:57PM -0800, Stephen Neuendorffer wrote:
> I was misled by the prior language. I've attempted to clarify how
> 'ranges' are used, in particular, how to get an identity mapping.
>
> Signed-off-by: Stephen Neuendorffer <stephen.neuendorffer@xilinx•com>
Acked-by: David Gibson <david@gibson•dropbear.id.au>
Thanks for the update. I particularly dislike the "1:1" terminology,
because in maths-speak *any* ranges translation is 1:1, unless it
includes overlapping ranges.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: Type: text/html, Size: 2029 bytes --]
prev parent reply other threads:[~2007-12-04 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 1:08 [PATCH] [POWERPC] [v2] Improved documentation of device tree 'ranges' Stephen Neuendorffer
2007-12-04 2:40 ` David Gibson
2007-12-04 3:22 ` Grant Likely
2007-12-04 5:27 ` Stephen Neuendorffer [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=20071204053148.C2FBCF00059@mail199-blu.bigfish.com \
--to=stephen.neuendorffer@xilinx$(echo .)com \
--cc=david@gibson$(echo .)dropbear.id.au \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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