From: Zang Roy-r61911 <tie-fei.zang@freescale.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/2]: Document the global utilities node define and example
Date: 19 Jun 2007 17:41:00 +0800 [thread overview]
Message-ID: <1182246060.3878.1.camel@localhost.localdomain> (raw)
In-Reply-To: <b653522c06e6053167988bb8bcf3a868@kernel.crashing.org>
On Tue, 2007-06-19 at 16:49, Segher Boessenkool wrote:
> > Document the global utilities node define and example.
> > Signed-off-by: Roy Zang <tie-fei.zang@freescale.com>
>
> Acked-by: Segher Boessenkool <segher@kernel.crashing.org>
>
> Thanks for documenting this stuff. One nit though...
>
> > + global-utilities@e0000 { /* global utilities reg */
>
> s/reg/block/ . It's not a single 32768 bit register I'm
> sure (how would you access it?!) :-)
I access it by a 32768 bit wide bus -:)!
Roy
prev parent reply other threads:[~2007-06-19 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 7:19 [PATCH 1/2]: Document the global utilities node define and example Zang Roy-r61911
2007-06-19 8:49 ` Segher Boessenkool
2007-06-19 9:41 ` Zang Roy-r61911 [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=1182246060.3878.1.camel@localhost.localdomain \
--to=tie-fei.zang@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=segher@kernel.crashing.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 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).